[parsec-users] Dedup number of threads

Christian Bienia cbienia at CS.Princeton.EDU
Wed Apr 15 12:09:59 EDT 2009



Just set "-t" equal to the number of CPUs. If necessary the system can then
work with all CPUs in the same pipeline stage so that no artificial
bottlenecks are introduced. The OS scheduler should figure out how many
threads are needed for each stage and the system should stabilize around the
ideal thread ratios for maximum throughput. This is how I did it for the
PARSEC papers.


- Chris



From: parsec-users-bounces at lists.cs.princeton.edu
[mailto:parsec-users-bounces at lists.cs.princeton.edu] On Behalf Of Nikolay
Sent: Wednesday, April 15, 2009 6:54 AM
To: parsec-users at lists.cs.princeton.edu
Subject: Re: [parsec-users] Dedup number of threads


Chris, could you please tell me, what number of threads per queue you used
in the PARSEC summary paper?
Performance greatly depends on value of the "-t" argument and I can't
understand how to find the optimal "-t" value.

Thanks in advance,

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cs.princeton.edu/pipermail/parsec-users/attachments/20090415/12d5ff15/attachment.htm>

More information about the parsec-users mailing list