Yes, we find its best to let users benchmark their code (if they
have it already) Or a code that uses similar algorithms. And then
have the user run on some machines we set aside.
While we are on the benchmark topic, Users might be interested, we
just installed a new set of Opteron 2220
Glad to contribute Victor!
I am running on a home workstation that uses an AMD 3800 cpu attached to
2 gigs of ram.
My timings for FT were 175 secs with one core and 110 on two cores with
-O3 and -mtune=amd64 as tuning options.
Brock, Terry and Jeff are all exactly correct in their comments
r
Thank you everybody for the advices.
I ran the NAS benchmark class B and it runs in 181
seconds on one core and in 90 seconds on two cores, so
it scales almost perfectly.
What were your timings, Jeff, and what processor do
you exactly have?
Mine is a Pentium D at 2.8GHz.
Victor,
Build the FT benchmark and build it as a class B problem. This will run
in the 1-2 minute range instead of 2-4 seconds the CG class A benchmark
does.
Jeff F. Pummill
Senior Linux Cluster Administrator
University of Arkansas
Terry Frankcombe wrote:
Hi Victor
I'd suggest 3 seconds
I agree. I like benchmarks to run 15 minutes to 24 hours.
Brock Palen
Center for Advanced Computing
bro...@umich.edu
(734)936-1985
On Jun 11, 2007, at 4:17 AM, Terry Frankcombe wrote:
Hi Victor
I'd suggest 3 seconds of CPU time is far, far to small a problem to do
scaling tests with. Even
Hi Victor
I'd suggest 3 seconds of CPU time is far, far to small a problem to do
scaling tests with. Even with only 2 CPUs, I wouldn't go below 100
times that.
On Mon, 2007-06-11 at 01:10 -0700, victor marian wrote:
> Hi Jeff
>
> I ran the NAS Parallel Bechmark and it gives for me
> -bash%/ex
Hi Jeff
I ran the NAS Parallel Bechmark and it gives for me
-bash%/export/home/vmarian/fortran/benchmarks/NPB3.2/NPB3.2-MPI/bin$
mpirun -np 1 cg.A.1
--
[0,1,0]: uDAPL on host SERVSOLARIS was unable to find
any NICs.
Another tr
Perfect! Thanks Jeff!
The NAS Parallel Benchmark on a dual core AMD machine now returns this...
[jpummil@localhost bin]$ mpirun -np 1 cg.A.1
NAS Parallel Benchmarks 3.2 -- CG Benchmark
CG Benchmark Completed.
Class =A
Size=14000
It
Not a dumb question at all. :-)
I think the problem is your L flag. Our mpif90 wrapper compiler should
already know where to find the MPI library, which is located in wherever you
installed openmpi. Your flag is trying to overload our settings and I
believe is causing confusion.
So just eliminat
Just remove the -L and -l arguments -- OMPI's "mpif90" (and other
wrapper compilers) will do all that magic for you.
Many -L/-l arguments in MPI application Makefiles are throwbacks to
older versions of MPICH wrapper compilers that didn't always work
properly. Those days are long gone; mos
10 matches
Mail list logo
