🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

3 total messages Started by Franklin Antonio Sun, 10 Jan 1993 23:28
alpha performance question
#61
Author: Franklin Antonio
Date: Sun, 10 Jan 1993 23:28
6 lines
694 bytes
I haven't seen any performance benchmark data on alpha-based machines
posted by users.  Has someone done some measurements of speed of some
program you've ported to an alpha-based machine vs same running on some
model of VAX?  ..or even some other brand?

If you are able to publish same, I would like to see it.
Re: alpha performance question
#65
Author: Richard Seymour
Date: Mon, 11 Jan 1993 19:24
34 lines
2605 bytes
In article <1993Jan10.232804.1030@qualcomm.com> antonio@qualcomm.com (Franklin Antonio) writes:
>I haven't seen any performance benchmark data on alpha-based machines
>posted by users.  Has someone done some measurements of speed of some
>program you've ported to an alpha-based machine vs same running on some
>model of VAX?  ..or even some other brand?

we managed to borrow an AXP 3000/500 for the two weeks ending Jan 6th.
ooohhhh... although most of our people we gone for the holidays, the few
 who remained reported fifty times faster performand than a VAXstation 3100/38,
 and five to seven times faster than an HP 9000/710.
These were biggy Fortran number-crunch, with lots of transcendental-routine
 calling deep in the loops. (which kills HP's)
The machines in question were: VAXstation 3100/38, 8mb
  Alpha AXP  3000/500, 96mb, dual 400mb disk (the OpSys and Fortran FILLED one)
  HP 9000/710, 48mb, 1Gb disk.
The program which got the most use repetitively runs thru a 50k block file.
 The Alpha showed 30% idle-time , which i assume was waiting for the disk.
Other users also reported the 50x factor over the 3100.
We also tried a program against an 11/780.  Due to an undiscovered bug,
 we had to run it non-optimized on the ALPHA.  it was still 68x faster.

But- if you want an Alpha to reaaaallllyyyy  drag, try WATCH under DEBUG.
They apparently don't have the memory-locking hardware trap a VAX does.
They -trace- every instruction as it executes to see if it modifies the 
 WATCHed locations.  very, very, VERY slow...

We also ran into a Open/Closed VMS difference: the LIB$FIXUP_FLT and its
 kin don't work under OpenVMS AXP (which is explained in HELP.. VERY good
 cross-platform HELP information... kudos to DEC)
We also tried joining it to our cluster (of course!), but LMF got upset.
It -did- manage to join (for a few seconds), and the cluster manager 
complained about differing VMS version numbers (what? OpenVMS V1.0 not 
the same as A5.5-2??)
--dick (i want one (or two, or three...))
Re: alpha performance question
#68
Author: Ehud Gavron 602-570-2000 x. 2546
Date: Tue, 12 Jan 1993 15:15
32 lines
1509 bytes
In article <1ishhcINNdhd@shelley.u.washington.edu>, seymour@stein.u.washington.edu (Richard Seymour) writes...
#We also tried joining it to our cluster (of course!), but LMF got upset.

I don't know why.  Ah... ahh... I'm going to sneeze... ahhh ahh...
I'm going to sneeze.... Look out:

$ LICENSE REGISTER VMSCLUSTER -
        /ISSUER=DEC -
        /AUTHORIZATION=MAC-10-AK-47-WOOF -
        /PRODUCER=DEC -
        /UNITS=0 -
        /TERMINATION_DATE=30-JAN-1993 -
        /AVAILABILITY=E -
        /OPTIONS=(ALPHA,MOD_UNITS) -
        /CHECKSUM=2-GCDM-NEAJ-PKAN-FFFL

(CSLG never had it so good)

#It -did- manage to join (for a few seconds), and the cluster manager 
#complained about differing VMS version numbers (what? OpenVMS V1.0 not 
#the same as A5.5-2??)

	Yeah but it will live.  And the queueing system will use
	the old (5.4) format.  but it's just fine.

#--dick (i want one (or two, or three...))

	Ehud

--
Ehud Gavron        (EG76)     
gavron@vesta.sunquest.com
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads