1 o Major feature (main loop, CPU usage):
2 - Previously, tor would enable at startup all possible main loop event
3 regardless if it needed them. For instance, directory authorities
4 callbacks were fired up even for client only. We have now refactored this
5 whole interface to only enable the appropriate callbacks depending on what
6 are tor roles (client only, relay, hidden service, etc.). Furthermore,
7 these events now depend on DisableNetwork or the hibernation state in
8 order to enable them. This is a big step towards reducing client CPU usage
9 by reducing the amount of wake ups the daemon does. Closes ticket 25376