[tor-bugs] #23722 [Core Tor/Tor]: Somebody should profile a Tor 0.3.1.7 relay

[Tor Bug Tracker & Wiki]

#23722: Somebody should profile a Tor 0.3.1.7 relay
--------------------------+------------------------------------
 Reporter:  arma          |          Owner:  (none)
     Type:  enhancement   |         Status:  new
 Priority:  Medium        |      Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor  |        Version:
 Severity:  Normal        |     Resolution:
 Keywords:                |  Actual Points:
Parent ID:                |         Points:
 Reviewer:                |        Sponsor:
--------------------------+------------------------------------

Comment (by Hello71):

 Replying to [comment:5 nickm]:
 > Weird! Was the server seeing much traffic at the time? I'm surprised
 that none of the compression algorithms, digest algorithms, or AES
 appeared on profile.

 well, consensus updates are uncommon, and AES-NI is very fast. suppose
 that you get https://calomel.org/aesni_ssl_performance.html performance,
 then if your relay is 100 megabit/sec and you can do 1700 megabyte/sec
 AES, then by my calculations, you should spend about 0.7% CPU time in AES.
 coincidentally, we have symbols in libcrypto.so at 0.60% and 0.54%.
 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1598529 is probably
 relevant, upgrading your kernel will probably help.

 as I said on IRC, KIST incidentally moderately improves CPU usage by
 calling epoll_ctl at a reasonable rate instead of the ridiculousness that
 was before.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/23722#comment:7>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online