Profile a 0.3.2.x fast relay

Following #23722 (moved), this is to try to learn if we have any regression or obvious performance issue from profiling in 032.

changed milestone to %Tor: 0.3.4.x-final

added 034-removed-20180328 034-triage-20180328 component::core tor/tor milestone::Tor: 0.3.4.x-final owner::dgoulet priority::medium profiling resolution::fixed severity::normal status::closed tor-relay type::task labels

After 3 hours of profiling a fast Exit relay on 032:

   2.33%  tor      tor                    [.] connection_bucket_refill
   1.73%  tor      tor                    [.] curve25519_donna
   1.43%  tor      [kernel.kallsyms]      [k] irq_entries_start
   0.97%  tor      [kernel.kallsyms]      [k] copy_user_generic_string
   0.92%  tor      [kernel.kallsyms]      [k] __fget
   0.91%  tor      tor                    [.] circuit_receive_relay_cell
   0.87%  tor      libc-2.24.so           [.] malloc
   0.76%  tor      libevent-2.0.so.5.1.9  [.] _init
   0.75%  tor      tor                    [.] buf_datalen
   0.70%  tor      [kernel.kallsyms]      [k] sys_epoll_ctl
   0.65%  tor      libevent-2.0.so.5.1.9  [.] evmap_io_active
   0.60%  tor      libevent-2.0.so.5.1.9  [.] event_base_loop
   0.56%  tor      [kernel.kallsyms]      [k] __raw_callee_save___pv_queued_spin_unlock
   0.55%  tor      tor                    [.] channel_flush_from_first_active_circuit
   0.54%  tor      libc-2.24.so           [.] 0x0000000000078d6a
   0.52%  tor      [kernel.kallsyms]      [k] update_cfs_shares
   0.51%  tor      tor                    [.] rep_hist_note_or_conn_bytes
   0.51%  tor      [kernel.kallsyms]      [k] sock_poll
   0.47%  tor      tor                    [.] circuit_get_by_circid_channel
   0.46%  tor      tor                    [.] tor_memcmp
   0.45%  tor      tor                    [.] assert_circuit_ok
   0.43%  tor      tor                    [.] buf_assert_ok
   0.42%  tor      [kernel.kallsyms]      [k] ipt_do_table
   0.41%  tor      tor                    [.] smartlist_contains
   0.41%  tor      libcrypto.so.1.1       [.] CRYPTO_ctr128_encrypt_ctr32

Nothing too crazy about those results imo.

Is that a fast relay that was relaying a lot of traffic at the time? Or was it ramping up?

Replying to nickm:

Is that a fast relay that was relaying a lot of traffic at the time? Or was it ramping up?

Fast relaying fast at the time. It is: http://52g5y5karruvc7bz.onion/#details/FDAED15C98CFE7A416E5676F614254F78406105C

FYI, I'll do this again with our release candidate in December.

These feature and bugfix tickets have no patches. The earliest they will get done is 0.3.4.

Trac:
Milestone: Tor: 0.3.2.x-final to Tor: 0.3.4.x-final

Trac:
Keywords: N/A deleted, 034-triage-20180328 added

Per our triage process, these tickets are pending removal from 0.3.4.

Trac:
Keywords: N/A deleted, 034-removed-20180328 added

Trac:
Resolution: N/A to fixed
Status: assigned to closed

closed

moved to tpo/core/tor#24127 (closed)