[parsec-users] Inputs sets and number of threads.

Vidyabhushan Mohan mohan at cs.virginia.edu
Sun Apr 25 19:24:39 EDT 2010


Thanks a lot Chris. That explains the difference.

-Bhushan

2010/4/25 Christian Bienia <cbienia at cs.princeton.edu>

>  Hi Bhushan,
>
>
>
> The input size and the number of threads are two independent parameters.
> The only thing you need to consider is that you want to make sure the input
> contains enough work units to keep all threads busy. Besides that you can
> scale the number of threads any way you want.
>
>
>
> Typically you would pick the largest input set that you can still run and
> then vary the number of threads any way you want. Please be aware that
> changing input sets also changes the program characteristics slightly.
>
>
>
> Best,
>
> Chris
>
>
>
>
>
> *From:* parsec-users-bounces at lists.cs.princeton.edu [mailto:
> parsec-users-bounces at lists.cs.princeton.edu] *On Behalf Of *Vidyabhushan
> Mohan
> *Sent:* Saturday, April 24, 2010 1:42 AM
> *To:* parsec-users at lists.cs.princeton.edu
> *Subject:* [parsec-users] Inputs sets and number of threads.
>
>
>
> Hi,
>
> Can anyone explain the difference between number of threads and input sets?
> For example, I run blackscholes as follows:
>
> For test input size:
> ./blackscholes 16 in_4.txt prices.txt
> For simlarge:
> ./blackscholes 16 in_64K.txt prices.txt
>
> I understand that the second parameter changes according to the input size,
> whereas the first parameter is the number of threads.
> So should I scale the number of threads according to the size of the input?
> Or is my above usage, where I keep the number of threads the same
> irrespective of the input size valid? If scaling the number of threads is
> necessary, how do I change the number of threads wrt to input size for the
> different benchmarks?
>
> Thanks!
>
> -Bhushan.
>
> _______________________________________________
> parsec-users mailing list
> parsec-users at lists.cs.princeton.edu
> https://lists.cs.princeton.edu/mailman/listinfo/parsec-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cs.princeton.edu/pipermail/parsec-users/attachments/20100425/0a357125/attachment.htm>


More information about the parsec-users mailing list