Opened 9 years ago

Last modified 7 years ago

#1229 closed defect (Not a bug)

cpu affinity cpuworker threads

Reported by: Falo Owned by:
Priority: Low Milestone:
Component: Core Tor/Tor Version: 0.2.2.7-alpha
Severity: Keywords:
Cc: Falo, Sebastian, nickm Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

v0.2.2.6-alpha on Debian Squeeze x86_64

On Blutmagie exit node I recently noticed all onionskin cpuworker threads _always_ run on
the same core as the main thread. Don't know if this is can be considered a bug, but it
renders the Numcpu config option pretty useless.

Olaf

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ P COMMAND

25495 debian-t 20 0 987m 567m 27m R 95.7 14.3 11369:12 0 tor

7328 debian-t 20 0 987m 567m 27m S 2.7 14.3 15:04.47 0 tor
7330 debian-t 20 0 987m 567m 27m S 2.3 14.3 15:59.22 0 tor

1 root 20 0 10324 684 572 S 0.0 0.0 1:32.45 1 init

[...]

[Automatically added by flyspray2trac: Operating System: Other Linux]

Child Tickets

Change History (4)

comment:1 Changed 9 years ago by Falo

nailing cpuworker and main thread to different cores using taskset command works

comment:2 Changed 9 years ago by Falo

pls forget this task. Don't know what has been up with my task scheduler. Restarting with v0.2.2.7-alpha the threads now are spread over all cores.

comment:3 Changed 9 years ago by nickm

flyspray2trac: bug closed.
closing by request

comment:4 Changed 7 years ago by nickm

Component: Tor RelayTor
Note: See TracTickets for help on using tickets.