[parsec-users] running parsec on Opteron

Mahmood Naderan nt_mahmood at yahoo.com
Sat Jun 11 06:54:36 EDT 2011


>You appear to be running simlarge in this case, which will end quickly on any relatively modern computer
 
the native input took 50 seconds and while the benchmark was running, I watched "top" all the time. The "%CPU" column is interesting. It says about 386%
 
PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
11612 mahmood   20   0  309m 150m 1268 S  386  0.5   0:15.22 x264

> Also, how are you compiling this benchmark? Are you using GCC

I used the AMD64 binaries from PARSEC site (~/parsec-2.1/pkgs/apps/x264/inst/amd64-linux.gcc.pre/bin/)

>One more way is that you can see the a directory per thread under /proc/<pid>/task

I see this

mahmood at srv:~$ ls /proc/11612/task/
11612  12060  12062  12064

So it shows 4 threads. Is that right?
// Naderan *Mahmood;

From: Joseph Greathouse <jlgreath at umich.edu>
To: Mahmood Naderan <nt_mahmood at yahoo.com>; PARSEC Users <parsec-users at lists.cs.princeton.edu>
Sent: Friday, June 10, 2011 11:53 PM
Subject: Re: [parsec-users] running parsec on Opteron

You appear to be running simlarge in this case, which will end quickly on any relatively modern computer. If this is the case, top might not even update the screen past 100% before the process ends, instead showing the CPU usage for the setup time.

Have you tried running this with the native input size using:
./x264 --quiet --qp 20 --partitions b8x8,i4x4 --ref 5 --direct auto --b-pyramid --weightb --mixed-refs --no-fast-pskip --me umh --subme 7 --analyse b8x8,i4x4 --threads 4 -o eledream.264 /z/jlgreath/parsec-2.1/pkgs/apps/x264/inputs/eledream_1920x1080_512.y4m

This may cause the benchmark to take long enough that top shows the CPU usage you're expecting.

Also, how are you compiling this benchmark? Are you using GCC?

-Joe

Quoting Mahmood Naderan <nt_mahmood at yahoo.com>:

> 
>> 1) How many cores per CPU in your machine?
> 
> 4
> 
>> 2) How many CPUs in your machine?
> 
> 2
> 
>> 3) How do you know that only one processor is allocated to x264?
> 
> I ran "top" in session #1 and
> "./x264 --quiet --qp 20 --partitions b8x8,i4x4 --ref 5 --direct auto --b-pyramid --weightb --mixed-refs --no-fast-pskip --me umh --subme 7 --analyse b8x8,i4x4 --threads 4 -o eledream.264 eledream_640x360_128.y4m" in session #2
> 
> // Naderan *Mahmood;
> 
> From: kishore kumar <kishoreguptaos at gmail.com>
> To: Mahmood Naderan <nt_mahmood at yahoo.com>; PARSEC Users <parsec-users at lists.cs.princeton.edu>
> Sent: Friday, June 10, 2011 5:37 PM
> Subject: Re: [parsec-users] running parsec on Opteron
> 
> 
> Hi,
> Can you give the following information to resolve your issue?
> 1) How many cores per CPU in your machine?
> 2) How many CPUs in your machine?
> 3) How do you know that only one processor is allocated to x264?
> 
> Best,
> Kishore
> 
> 
> 
> On Fri, Jun 10, 2011 at 1:07 AM, Mahmood Naderan <nt_mahmood at yahoo.com> wrote:
> 
> Hi
>> I ran some PARSEC benchmarks on an Opteron processor to see if increasing the number of threads can allocate more processors. For example, I ran x264 with one thread and saw that only one cpu is allocated. Next when I ncreased the number of threads to 4, I saw again that only one cpu is allocated.
>>  
>> How one can exaplain that behaviour? Thanks for any suggestion
>> 
>> // Naderan *Mahmood;
>> _______________________________________________
>> 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/20110611/fba3ec80/attachment.htm>


More information about the parsec-users mailing list