Opened 12 years ago

Last modified 8 years ago

#884 closed defect (Deferred)

NumCPUs not working

Reported by: Mave Owned by:
Priority: Low Milestone:
Component: Core Tor/Tor Version:
Severity: Keywords:
Cc: Mave, nickm Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


the Version I use can't be selected here. Its (r17346) (downloaded today on โ€‹

I tryed it 2 ways. First by installing Tor via Debian apt and setting "NumCPUs 4" and second by manualy building tor from the sources.
No way brings tor to spawn workers and use the cpu power for the other cores.
I think this is a heavy Performance Problem because today there are only multicore cpus for sale! Because of this
problem I have to start 4 instances of TOR in order to get the ressurces used.

Kernel Version: x86_64

[Automatically added by flyspray2trac: Operating System: Other]

Child Tickets

Change History (5)

comment:1 Changed 12 years ago by nickm

Known issue; right now, only the in-Tor public key operations are farmed to the worker threads. We need to get
AES operations and OpenSSL operations distributed across worker threads as well, but that will take a fair bit
of coding.

comment:2 Changed 12 years ago by nickm

Oh! Also, Tor isn't supposed to fork into multiple processes it's multithreaded instead.

comment:3 Changed 12 years ago by nickm

I'm closing this as "Deferred." It's already in the TODO.021 list of things that would be nice to get into 0.2.1.x-final,
and if we don't get to it by then, I hope we can get to it in the next version.

If anybody wants to try working on this, I've already added some description to TODO.021 of what I think the right
architecture for parallelizing the AES across cores would be.

comment:4 Changed 12 years ago by nickm

flyspray2trac: bug closed.

comment:5 Changed 8 years ago by nickm

Component: Tor Relay โ†’ Tor
Note: See TracTickets for help on using tickets.