blade vs. DS10 on "mybenchmark"
David Mathog
"mybenchmark" (http://seqaxp.bio.caltech.edu/pub/software/mybenchmark.zip)
and have been added to the table. My thanks to Brian Stretch
(bstr...@mindspring.com) and Paul Joslin (paul....@suncor3.sdrc.com)
for running these. Results for a VAX 4000 were reported "Barry Treahy,
Jr." <tre...@mmaz.com> and have also been added.
Note that contrary to some of my former statements the Unix
machines are not (apparently) all using file caching to obtain the
speeds obtained on /tmp - but caching on the drive itself is enabled. The
test file created by maketest is 8326000 bytes long - do the math to get the
actual write speeds observed.
The STREAM benchmark for a Blade 100 is about 4 times lower than on a DS10,
but the $1000 "vanilla" blade still moves data to disk (or at least the
memory cache on the disk) many times faster than heavily optimized IO can
on a DS10 running VMS. And it does it using an ATA disk. A DS10 running
Linux or Tru64 - and using uw or u2w scsi, is faster than a blade though.
(No big surprise there.)
I don't expect shame (or anything else) from Compaq management, but I hope
that the folks in VMS engineering are suitably red faced that
this el cheapo Sun system just wiped the floor with the VMS DS10 with
respect to disk IO. (And price.)
Regards,
David Mathog
mat...@seqaxp.bio.caltech.edu
Manager, sequence analysis facility, biology division, Caltech
**************************************************************************
This is a table showing MYBENCHMARK speeds on a variety
of platforms. Times shown are in seconds. The tests are
from the MYBENCHMARK suite which measure various aspects
of "disk" I/O and file caching performance.
Tests to local disks:
maketestf mystart myread mysplit Disk OS Hardware
Notes maketest myopenin myopen mysplitbinary
--------------------------------------------------------------------------------
2 - 0.33 0.01 0.01 0.17 0.17 0.41 1.14 /tmp Linux64 Blazer Itanium (666Mhz)
3 - 0.42 0.00 0.00 0.28 0.24 0.64 0.62 /tmp RH 7 Proliant 550 (450Mhz)
5 0.90 0.40 0.00 0.00 0.20 0.20 0.70 1.30 /tmp SunOS 5.7 Ultra60 (360 Mhz)
18 1.50 0.30 0.00 0.00 0.10 0.20 1.50 1.30 /tmp SunOS 5.8 Blade 100 (500 Mhz)
7 2.90 0.20 0.00 0.00 0.10 0.10 0.50 0.30 /tmp Tru64 DS10L (466 Mhz)
9 3.40 0.20 0.00 0.00 0.10 0.10 0.60 0.30 /tmp Tru64 DS20 (500 Mhz)
12 1.46 0.29 0.00 0.00 0.14 0.11 0.40 0.37 /tmp RH 6.2 DS10 (466 Mhz)
16 - 0.43 0.01 0.01 0.30 0.64 1.10 0.97 RAM VMS 7.2-1 DS10 (466 Mhz) (FASTRMS)
11 19.85 1.36 0.02 0.01 0.20 4.46 7.76 7.94 local OVMS7.3FT DS10L (466 Mhz)(FASTRMS)
15 - 1.77 0.02 0.04 0.47 9.05 16.62 14.38 local VMS 7.2-1 DS10 (466 Mhz) (FASTRMS)
14 - 26.46 0.11 0.01 0.54 7.75 46.51 39.10 local VMS 7.2-1 DS10 (466 Mhz) (Vanilla)
17 12.18 9.51 0.13 0.18 6.13 9.21 19.61 16.27 local VMS 7.2 VAX 4000/100 (FASTRMS,RAID)
Tests to networked disks:
maketestf mystart myread mysplit Disk OS Hardware
Notes maketest myopenin myopen mysplitbinary
--------------------------------------------------------------------------------
1 - 2.29 0.01 0.01 1.14 1.40 5.49 4.67 NFS Linux64 Blazer Itanium (666Mhz)
4 1.20 0.70 0.00 0.00 3.60 0.50 1.70 3.80 NFS SunOS 5.7 Ultra60 (360 Mhz)
6 3.50 1.50 0.00 0.00 0.10 2.10 6.00 4.70 NFS Tru64 DS10L (466 Mhz)
8 3.50 1.40 0.00 0.00 0.10 2.20 6.20 4.70 NFS Tru64 DS20 (500 Mhz)
10 35.57 34.33 0.03 0.02 0.20 5.55 43.27 40.24 MSCP OVMS7.3FT DS10L (466 Mhz) (FASTRMS)
1. Linux64 on a Blazer Itanium (666Mhz) - the Compaq testdrive system.
Using /home (NFS mounted from spe253) . 08-FEB-2001
2. Linux64 on a Blazer Itanium (666Mhz) - the Compaq testdrive system.
Using /tmp . 08-FEB-2001
3. RedHat7 on a Proliant 5500 (450Mhz) - the Compaq testdrive system.
Using /tmp . 08-FEB-2001
4. SunOS 5.7 on an Ultra60 (360 Mhz) - the Caltech ITS "clyde" system.
Using /home (NFS mounted). 02-MAR-2001
5. SunOS 5.7 on an Ultra60 (360Mhz) - the Caltech ITS "clyde" system.
Using /tmp. 02-MAR-2001
6. Tru64Unix 5.1 on a DS10L (466Mhz) - the Compaq testdrive system.
Using /usr/bin/time on the login directory which is on /home, which
in NFS mounted and served from "spe253". 08-FEB-2001
7. Tru64Unix 5.1 on a DS10L (466Mhz) - the Compaq testdrive system.
Using /usr/bin/time on the /tmp directory. 08-FEB-2001
MAKETESTF: Creating test file, fortran
8. Tru64Unix 5.1 on a DS20 (500Mhz) - the Compaq testdrive system.
Using /usr/bin/time on the login directory which is on /home, which
in NFS mounted and served from "spe253". 08-FEB-2001
9. Tru64Unix 5.1 on a DS20 (500Mhz) - the Compaq testdrive system.
Using /usr/bin/time on the /tmp directory. 08-FEB-2001
MAKETESTF: Creating test file, fortran
10. OpenVMS 7.3 field test on a DS10L (466Mhz) - the Compaq testdrive system.
Using USER1 login directory which is served from VMSSERV which is
an AlphaServer 1200 5/400 and the device is a DEC RZ1CB-CA.
FASTRMS variant of these programs. 08-FEB-2001
11. OpenVMS 7.3 on a DS10L (466Mhz) - the Compaq testdrive system.
Using $2$DKA100, which is a SCSI disk on "spe202". Using FASTRMS
variants. 09-FEB-2001
12.Redhat 6.2 on a DS10 (466Mhz U2W disks) - my "barrel" system,
Using /usr/bin/time on the /tmp directory. 08-FEB-2001
14. OpenVMS 7.2-1 on a DS10 (466 Mhz U2W disks). "seqaxp" system.
RMS set to defaults. No FASTRMS settings.
15. OpenVMS 7.2-1 on a DS10 (466 Mhz U2W disks). "seqaxp" system.
RMS set to defaults. FASTRMS settings.
16. OpenVMS 7.2-1 on a DS10 (466 Mhz U2W disks). "seqaxp" system.
RMS set to defaults. FASTRMS settings. On a RAMDISK
17. OpenVMS 7.2, VAX 4000/100, no VIOC or third party disk caching,
and all storage connected via standard 8-bit internal SCSI-1 bus to
a Infrotrends RAID array OpenVMS 7.2 on VAX 4000/100. FASTRMS variant.
RMS block=0/buffer=0/extend=64. Barry Treahy, Jr. <tre...@mmaz.com>
18. SunOS 5.8, Sun Blade 100, 128Mb RAM, UltraSparcIIe 500 Mhz,
by Brian Stretch (bstr...@mindspring.com). Similar results
reported by Paul Joslin (paul....@suncor3.sdrc.com). 08-MAR-2001.
Note that mysplit results reproted by both testers showed user:0.3 and
sys:0.1, leaving the other .9 seconds unaccounted for.
Alan Greig
Mathog) wrote:
>Note that contrary to some of my former statements the Unix
>machines are not (apparently) all using file caching to obtain the
>speeds obtained on /tmp - but caching on the drive itself is enabled. The
>test file created by maketest is 8326000 bytes long - do the math to get the
>actual write speeds observed.
I think you can enable disk hardware caching using the sys$etc:*scsi*
utilities - unsupported of course. If true you might want to try this
if anyone can provide the appropriate arguments.
--
Alan
Darren Peacock
Good news , I just tuned my Alphastation 200/233 with a single scsi
disk
I changed the block size on the and the block read size from the disk and
block write size, I also changed the My benchmark program to utlize an rms
call rather than the standrad C , that way the UNix write and the VMS write
are the same.
And the figures exceeded the little blade exceeded .
Have seen this benchmark posted before, and I mentioned that it was not an
apples to apples, the easiest thing to do is set the VMS system to reflect
the UNix Op setup.
"David Mathog" <mat...@seqaxp.bio.caltech.edu> wrote in message
news:988qcu$h...@gap.cco.caltech.edu...