[Info-vax] Some VMS/x86 perf test data from WASD maintainer.

[Mark Daniel]

On 27/4/2023 8:35 pm, Volker Halle wrote:
> Jan-Erik Söderholm schrieb am Donnerstag, 27. April 2023 um 11:24:46 UTC+2:
> 
> After now also running a VSI OpenVMS x86-64 E9.2-1 system (using VMware Workstation Player 16) and installing the C compiler, I have tried to 'calibrate' the procedure to obtain the VUPS values for x86-64 using the PRIME_SIEVE.C tool (calculating prime numbers up to  10^10). The CPU_MULTIPLIER value for x86_64 should be set to 8 - you can easily edit this procedure to add (at the right place):  $ IF F$GETSYI("ARCH_NAME").EQS."x86_64" THEN $ cpu_multiplier=8

With the VUPS.COM procedure modified to

|$ cpu_multiplier = 10 ! VAX = 10 - Alpha/AXP = 40
|$ if f$getsyi("arch_name").eqs."x86_64" then $ cpu_multiplier=8

the resultant

|X86VMS$ @vups.com
|innotek GmbH VirtualBox with 2 CPU and 7574MB running VMS V9.2
|Approximate System VUPs Rating : 225.6 ( min: 224.4 max: 226.2 )

down from 272 "VUPs" reported previously, on a commodity DELL SFF with 
Windows 10 Pro Version 22H2

Processor	Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz   3.60 GHz
Installed RAM	16.0 GB

> The resulting VUPS values for x86-64 are now more realistic:   5900 VUPS  on an i5-9600K CPU @3.7 GHz
> 
> On this OpenVMS x86_64 system, PRIME_SIEVE needs 19.34 sec to calculate primes up to 10^10. On an ES45 Model 2B (EV68CB 1250 MHz) system it took 49.04 seconds, that system was measured at 2414 VUPS.
> 
> See previous discussion in: https://groups.google.com/g/comp.os.vms/c/ouhZ7C7bgoQ/m/_iEqNzm1AwAJ
> 
> PRIME_SIEVE was obtained from http://wwwhomes.uni-bielefeld.de/achim/prime_sieve.html
> 
> Volker.

-- 
Anyone, who using social-media, forms an opinion regarding anything 
other than the relative cuteness of this or that puppy-dog, needs 
seriously to examine their critical thinking.