[parsec-users] Simulation time of "facesim" and "vips"
Muhammad abid Mughal
mabidm_pieas at yahoo.com
Tue Jun 1 01:34:49 EDT 2010
Hi Jim Dempsey,
Thanks for quick response.
I have already successfully run "facesim" and "vips" using "parsecmgmt -a run -p vips -c gcc-hooks -i simsmall -n 8 -x pre-simics" command on
my real sun machine and simulated machine inside simics (ie functonal simulation).In addition, i disabled all SMF services of solaris 10 inside my
simulated machine so that these services don't interfere with my PARSEC benchmark.
As far as i understand your response you are asking me to Optimize I/O of "facesim" and "vips" using actual and virtual time.
My simulated machine is 8-chip distributed shared memory machine and i am working on prefetching/memory streaming using Hardware Prefecher.
I am confused because i was planning to run simulations using "simmedium" data set but i would not be possible because of simulation speed.
I am wondering if i increase number of threads for facesim and vips to finish simulation quickly. Any more suggestion.
From: Jim Dempsey <jim at quickthreadprogramming.com>
To: PARSEC Users <parsec-users at lists.cs.princeton.edu>
Sent: Tuesday, June 1, 2010 11:39:56
Subject: Re: [parsec-users] Simulation time of "facesim" and "vips"
Have you verified first that your configuration runs well in
native mode on an x86 processor? This is to make sure your input data and
command line arguments are correct. And will give you a base line measurement
for a given processor model.
The next thing to do is look at the major loop in facesim to
see if you can instrument that in native mode. e.g. on the native mode run, use
RDTSC (or other high precision timer) and record the time intervals for each
iteration of the major loop. After you have this collection of times (convert to
seconds) then recode to use a virtual timer in your simulation mode, however
also modify the simulator such that you get progress information such as the
virtual time elapsed .AND. the actual time elapsed at each major loop interval.
Now then instead of running simulation to end of benchmark program, you can run
the simulation for as many iterations as you deem practical and which provides
the timing information you want.
Also, while you are adding your RDTSC insturmentation, measure
the time for each file I/O. Then you can use this data to normalize the I/O
within the simulator.
From: parsec-users-bounces at lists.cs.princeton.edu
[mailto:parsec-users-bounces at lists.cs.princeton.edu] On Behalf Of Muhammad abid Mughal
Sent: Monday, May 31, 2010 8:32
To: Parsec group
Subject: [parsec-users] Simulation time
of "facesim" and "vips"
Hope you all doing good. I am running timing simulation of
above-said benchmarks using "simsmall" data set.
But its been running for almost 7 days. Is there anyway to reduce this huge
simulation time for these benchmarks without compromising on the performance
measurement accuracy? ie performance measurement must be representative of the
work done by these benchmarks.
i find it hard to switch to another Simulator fast simulator (ie Flexus) .
I am using GEMS simulator.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the parsec-users