--D6IIOQQv2Iwyp54J
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Aug 22, 2005 at 01:56:46AM +0200, Johnny Billquist wrote:
> On Sun, 21 Aug 2005, Sean Davis wrote:
>=20
> > On Mon, Aug 22, 2005 at 01:29:04AM +0200, Johnny Billquist wrote:
> > > On Sun, 21 Aug 2005, Jochen Kunz wrote:
> > >
> > > > On Sun, 21 Aug 2005 02:32:35 +0200
> > > >
> > > > I leave it to your homework to calculate estimated build times base=
d on
> > > > the MIPS numbers. ;-)
> > >
> > > I can also tell that on a VAX-8650, it takes a little over a week
> > > nowadays.
> > > In speed comparision, a VAX-8650 is about 6 VUPS (maybe a bit more), =
while
> > > the 11/750 is the same 0.65 VUPS. That would leave us somewhere aroun=
d 11
> > > weeks. Now, an 11/750 can't have more than 14 megs of physical memory=
 (or
> > > something like it), which means it will probably be even worse.
> >
> > Has anybody written anything to benchmark a machine in VUPS? I'd be
> > interested to know how many VUPS an Athlon gets, or an Opteron ;)
>=20
> Doubt there would be a point to it, since you don't have the same
> instructions. VUPS is mostly meaningful to compare different VAXen, since
> that will tell you how fast the same code would execute on different
> machines. Binary code, that is.

Well, there is the concept of running the VAX simulator on those systems.=
=20
And given how CPU performance had grown over time, it could make for some=
=20
fast VAX systems. :-)

Take care,

Bill

--D6IIOQQv2Iwyp54J
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)

iD8DBQFDCozVWz+3JHUci9cRAnKrAJ42LqPkeS9wi9XI8Yjyqp7nGj9JOgCfSXeB
gEfAI3EVC//9CsBNwsRz03I=
=F1+O
-----END PGP SIGNATURE-----

--D6IIOQQv2Iwyp54J--