[parsec-users] Running times of PARSEC workloads on Xeon 8-core, 8GB machine?

Christian Bienia cbienia at CS.Princeton.EDU
Tue Apr 20 12:57:19 EDT 2010

Hi Kishore,


That sounds about right. The runtime of the native input set was within 20
minutes when I defined it about 3 years ago. With a modern machine it will
be noticeably less.






From: parsec-users-bounces at lists.cs.princeton.edu
[mailto:parsec-users-bounces at lists.cs.princeton.edu] On Behalf Of kishore
Sent: Tuesday, April 20, 2010 12:52 AM
To: PARSEC Users
Subject: [parsec-users] Running times of PARSEC workloads on Xeon 8-core,
8GB machine?



Running-times of most of the PARSEC workloads (bodytrack, canneal etc.) on
my machines is within maximum of 10 minutes (in case of 1 to 8 threads) with
*native* inputs. My machine is a Xeon 8-core having 8GB Main memory. 

I am executing the workloads with parsecmgmt. For example:
 ./bin/parsecmgmt -a run -p streamcluster -c gcc-pthreads -i native -n
<number of threads>  (this is taking 720 seconds with 1-thread and 256
seconds with 8-threads)

Workloads such as bodytrack is taking 360 seconds with 1-thread and 68
seconds with 8-threads.

Is there anything wrong? or is this just because of system configuration?

Kishore Kumar Pusukuri

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

More information about the parsec-users mailing list