[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #4626 [Tor Directory Authority]: Very high cpu usage for gabelmoo running master
#4626: Very high cpu usage for gabelmoo running master
-------------------------------------+--------------------------------------
Reporter: Sebastian | Owner:
Type: defect | Status: new
Priority: normal | Milestone: Tor: 0.2.3.x-final
Component: Tor Directory Authority | Version:
Keywords: | Parent:
Points: | Actualpoints:
-------------------------------------+--------------------------------------
Comment(by Sebastian):
And I've managed to get the libc broken down. Looks like stuff from
outside Tor got put in. Here we go with a better profile.
{{{
samples % image name symbol name
816064 10.3630 tor sha1_block_data_order
326831 4.1503 tor lh_retrieve
270685 3.4374 libevent-2.1.so.1.0.0 event_base_loop
266122 3.3794 tor CRYPTO_THREADID_cmp
256188 3.2533 tor CRYPTO_lock
246810 3.1342 tor ssleay_rand_add
198834 2.5249 tor bn_mul_mont
176971 2.2473 tor EVP_DigestInit_ex
171173 2.1737 tor ssl3_read_n
156014 1.9812 tor ERR_clear_error
155584 1.9757 tor SHA1_Update
148804 1.8896 tor ssl3_read_bytes
144783 1.8386 libc-2.11.2.so memcpy
138239 1.7555 libevent-2.1.so.1.0.0
event_process_active_single_queue
121508 1.5430 libevent-2.1.so.1.0.0 epoll_dispatch
110935 1.4087 tor assert_connection_ok
108831 1.3820 tor connection_handle_write
104542 1.3276 libc-2.11.2.so _int_free
102253 1.2985 tor int_thread_get_item
98278 1.2480 libc-2.11.2.so malloc
97648 1.2400 libevent-2.1.so.1.0.0 event_pending
96666 1.2275 tor conn_write_callback
96345 1.2235 tor ssl3_setup_read_buffer
95187 1.2088 tor tor_tls_write
90558 1.1500 tor connection_bucket_round_robin
87150 1.1067 tor flush_buf_tls
86564 1.0993 tor SHA1_Final
85288 1.0831 libevent-2.1.so.1.0.0 gettime
83158 1.0560 libc-2.11.2.so memset
82328 1.0455 tor connection_bucket_write_limit
82056 1.0420 tor _log_fn
81218 1.0314 [vdso] (tgid:13332 range:0x7fff9719a000-0x7fff9719b000)
[vdso] (tgid:13332 range:0x7fff9719a000-0x7fff9719b000)
79000 1.0032 libc-2.11.2.so _int_malloc
76371 0.9698 tor ssl3_accept
72840 0.9250 tor ssl3_release_read_buffer
69932 0.8880 tor BIO_read
67766 0.8605 tor tor_addr_is_internal
66815 0.8485 tor get_error_values
65876 0.8365 libc-2.11.2.so __read_nocancel
64578 0.8201 libevent-2.1.so.1.0.0 event_queue_remove_active
63060 0.8008 tor EVP_DigestFinal_ex
62984 0.7998 tor ssl3_get_message
61671 0.7831 tor CRYPTO_malloc
60856 0.7728 tor SHA1_Init
60739 0.7713 libevent-2.1.so.1.0.0 evmap_io_active
57774 0.7337 tor CRYPTO_add_lock
57171 0.7260 tor EVP_MD_CTX_init
56716 0.7202 tor EVP_MD_CTX_cleanup
53904 0.6845 tor OPENSSL_cleanse
53697 0.6819 libc-2.11.2.so free
49858 0.6331 tor engine_table_select
49590 0.6297 tor ssl3_write_bytes
49328 0.6264 libc-2.11.2.so __epoll_wait_nocancel
48919 0.6212 libevent-2.1.so.1.0.0 event_active_nolock
47917 0.6085 tor assert_buf_ok
47879 0.6080 tor tor_tls_get_error
45525 0.5781 libc-2.11.2.so __errno_location
45152 0.5734 tor int_thread_get
45064 0.5723 libc-2.11.2.so read
43563 0.5532 tor sock_read
40059 0.5087 tor int_thread_release
39132 0.4969 tor ERR_get_state
38059 0.4833 tor SSL_get_error
}}}
I still have no idea what tor is actually *DOING* here, there is
absolutely no reason to spend all this cpu
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/4626#comment:7>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs