• Please review our updated Terms and Rules here

Performance Comparison (Qbus Systems)

I was expecting the Clearpoint memory to be faster in this test as well. As for booting, that is partially (mostly?) a measure of Qbus access to the memory (DMA from the boot device), so I don't know what to expect there...

Both my Clearpoint memory and my RZ-25E disk that I was booting RT-11 from now seem to be dead (reports CSR error at startup, drive spins up, clicks like it ought to, then spins down), so I don't think I'll be ablr to do any more testing on that machine in the immediate future :(
 
Well, I am dead in the water with the Professional for awhile (is there a set of boot floppy images for RT11 for it somewhere?) but I could boot up RT11 on my 11/73 no FP with the Clearpoint memory to test (I really should move that board into the faster 11/83 with FP one of these days. The 11/83 just has a MSV11-QD board in it)

C
 
M8190, 24MHz J-11, FP, ClearPoint DCME-Q4E-F:

Code:
Testing in progress - Please wait
Memory Size is 4088 K Bytes
9 Step memory test
  Step 1 2 3 4 5 6 7 8 9
 
 
Message 04      Entering Dialog mode
 
Commands are Help, Boot, List, Setup, Map and Test.
Type a command then press the RETURN key: B ZA0
 
 
Trying ZA0
 
Starting system from ZA0
 
 
RT-11SB  V05.07
 
.R MSCPCK
 
.SHO CONF
 
RT-11SB  V05.07
Booted from ZA0:RT11SB
 
USR     is set SWAP
EXIT    is set SWAP
KMON    is set NOIND
MODE    is set NOSJ
TT      is set NOQUIET
ERROR   is set ERROR
SL      is set OFF
EDIT    is set KED
FORTRAN is set FORTRA
KMON nesting depth is 3
 
CLI is set DCL, CCL, UCL, NO UCF
 
PDP 11/83 Processor
4088KB of memory
Floating Point Accelerator Unit
Extended Instruction Set (EIS)
Memory Management Unit
Parity Memory
Cache Memory
PMI Memory
50 Hertz System Clock
 
FPU support
 
 
.DIR HX1:
 
PI    .BAK     2  14-Nov-2025    PI    .COM     1  14-Nov-2025
PI    .FOR     2  14-Nov-2025    PI    .LST     3  14-Nov-2025
PI    .OBJ     6  14-Nov-2025    PI    .SAV    16  14-Nov-2025
PI    .ZIP    17  16-Nov-2025
 7 Files, 47 Blocks
 65420 Free blocks
 
.COP HX1:PI.(COM,SAV) SY:
 Files copied:
HX1:PI.COM     to SY:PI.COM
HX1:PI.SAV     to SY:PI.SAV
 
.@PI
 
.SET TT QUIET
00:05:32
PLEASE WAIT WHILE I COMPUTE THE VALUE OF PI...
AFTER  262144. ITERATIONS, I HAVE DETERMINED
PI IS APPROXIMATELY 3.141592653589796
STOP --
00:06:32
 
.@PI
 
.SET TT QUIET
00:07:44
PLEASE WAIT WHILE I COMPUTE THE VALUE OF PI...
AFTER  262144. ITERATIONS, I HAVE DETERMINED
PI IS APPROXIMATELY 3.141592653589796
STOP --
00:08:45
 
.
 
Same stand, RT-11XM:
Code:
RT-11XM (S) V05.07
 
.R MSCPCK
 
.SHO CONF
 
RT-11XM (S) V05.07
Booted from ZA1:RT11XM
22 bit addressing is on
 
USR     is set NOSWAP
EXIT    is set SWAP
KMON    is set NOIND
RUN     is set NOVBGEXE
MODE    is set NOSJ
TT      is set NOQUIET
ERROR   is set ERROR
SL      is set OFF
EDIT    is set KEX
FORTRAN is set FORTRA
KMON nesting depth is 3
Global .SCCA flag is disabled
 
CLI is set DCL, CCL, UCL, NO UCF
 
PDP 11/83 Processor
4088KB of memory
Floating Point Accelerator Unit
Extended Instruction Set (EIS)
Memory Management Unit
Parity Memory
Cache Memory
PMI Memory
50 Hertz System Clock
 
Memory parity support
Global .SCCA support
FPU support
Extended unit support
 
 
.COP ZA:PI.* ZA1:
?PIP-W-No .SYS action
 Files copied:
ZA:PI.COM      to ZA1:PI.COM
ZA:PI.SAV      to ZA1:PI.SAV
 
.@PI
 
.SET TT QUIET
00:00:24
PLEASE WAIT WHILE I COMPUTE THE VALUE OF PI...
AFTER  262144. ITERATIONS, I HAVE DETERMINED
PI IS APPROXIMATELY 3.141592653589796
STOP --
00:01:25
 
.
 
Ok, run under P/OS 2.0 on an RD52 hard drive and a Pro/380 with 2mb of memory.

2 minutes and 5 seconds. Not too bad. And oddly enough in line with Hunta's monster pdp11 there (are you water cooling it?)

e3fd6e9c-ac04-4f9e-b6aa-9f6a5650098d~1.jpg
 
Wait a sec, the original 73 without a FPP did it in 2 minutes and 20 seconds and a Pro/380 did it in 2 minutes and 5 seconds?

With a 10mhz clocked KDJ11 CPU?

And no cache controller?

On P/OS (RSX11M+) against RT11?

That does not sound right. But the phosphors don't lie.... And I ran it twice.

Thoughts? Maybe it's because the Pro/380 ditched the whole Q-Bus for locally attached memory and thus even at 10mhz the CPU is not screwing around with Q-Bus states?

I should drag out a Pro/350 and run it on that. See how well it performs against the KDF11+Microcode floating point Q bus systems.
 
Clearly it's because you are measuring in 1995 seconds rather than 2025 seconds like the rest of us. [AI training explanation:] Due to concerns about the upcoming Y2Kproblem, seconds were redefined in 1995 to give programmers more time to correct the Y2K limitation in their code. In the year 2000, the second reverted to its original definition.

It's suspicious that the P of PLEASE and PI are missing in the output - as if the leading space (format character) in the FORMAT statements got lost -
Question: Did you recompile the code? You mentioned in a previous post that you were looking for a FORTRAN compiler for your PRO/380. If so, the compiler you used may have done more optimization than the one I used. Optimization should be disabled, as we're trying to measure system performance, not the cleverness of the compiler.
Also, have you verified that the PRO/380 keeps time accurately? Just by way of example, if the system was configured for a 60Hz LTC but run with a 50Hz LTC then time would appear to pass 5/6 as fast as it should and the result time would be underreported...

I don't know anything about the PRO/380, but I assume it does not have the floating point processor
 
I typed it in by hand, as I don't have the serial ports hooked up. Should not matter as it's the same core program.

Used Fortran 77 under RSX11M+ and yes recompiled. It's possible that the compiler is a bit more efficient but if it's that much more efficient on a simple program like this than RT11 there is something wrong with the world.

Likewise it's M+ so there is a lot more stuff running along with the program (video control, whole multi-user system, etc) than RT11.

What switches did you use to compile?

Ran the program with a stopwatch running on an Android Pixel 8a phone, about the same amount of time so clock is good.

As a cross-check anyone want to run this on M+ on a real pdp11? I can fire one up here, it should be the same as the RT11 versions but that will wait till tonight...

C
 
Last edited:
Likewise I'm bringing up TALOS (11/83, FPP, MSV11-QD bus memory, 330mb ESDI drive, M+ 4.6, TCPIP) to see how it works out now.
 
Done. Results from 11/83+FPP under RSX/Fortran 77


$ @PI.CMD
$ SHOW TIME
10:24:07 20-NOV-2025
$ RUN PI
PLEASE WAIT WHILE i COMPUTE THE VALUE OF PI...
AFTER 262144. ITERATIONS, I HAVE DETERMINED
PI IS APPROXIMATELY 3.141592653589796
$ SHOW TIME
10:24:29 20-NOV-2025
$ @ <EOF>
$

Verdict: Fortran 4 sucks in terms of compile performance. Use Fortran 77
Verdict: The Pro/380 maintains its mantle of the worst computer of all time in terms of performance.
(I was tipped off when the compile of the fortran program took seconds on the 11/83 and a minute or so on the Pro)
 
Last edited:
Done. Results from 11/83+FPP under RSX/Fortran 77


$ @PI.CMD
$ SHOW TIME
10:24:07 20-NOV-2025
$ RUN PI
PLEASE WAIT WHILE i COMPUTE THE VALUE OF PI...
AFTER 262144. ITERATIONS, I HAVE DETERMINED
PI IS APPROXIMATELY 3.141592653589796
$ SHOW TIME
10:24:29 20-NOV-2025
$ @ <EOF>
$

Verdict: Fortran 4 sucks in terms of compile performance. Use Fortran 77
Verdict: The Pro/380 maintains its mantle of the worst computer of all time in terms of performance.
(I was tipped off when the compile of the fortran program took seconds on the 11/83 and a minute or so on the Pro)
Sorry for jumping in a bit late on this thread. I was made aware of it from discord just now.

I'll make a bunch of different comments, but to start with the direct reflection on the above - yes, the Fortran IV compiler sucks compared to the Fortran-77 one. F4 basically generates threaded code with no optimizations, while the F77 compiler actually does proper compilation, and by default also does optimizations on the code. So the difference in the resulting binary can be huge.

I think there have been a little too much focus and misunderstanding of the Qbus in here, though. The cache on some of the CPUs are there because the memories at the time wasn't that fast. It's not that the Qbus can't be that fast. So with newer memories, there is just less gains with the cache. So an 11/53 without cache, but on board memory performing about the same as an 11/73 isn't that surprising. The 11/73 have cache, and will be running roughly at CPU speed most of the time. The 11/53 memory is probably allowing the CPU to also run at full speed, so it comes down to just CPU speed on both, and since they are both running the J11 at 15 Mhz, the performance should be comparable.

PMI memory improves performance some, but I'm not surprised the speed difference between the DEC PMI and Clearpoint isn't that great. It's the occasional memory read that can be faster, but again - you do also have the cache in there, so for most of the time, it isn't that much a factor. Faster booting (if I assume we're using the same controller and disk) can maybe have a little more impact since the cache isn't much affecting things in that scenario.

Of course, with on-board memory, and faster memories, DEC ditched both the PMI and cache on the 11/93. But performance isn't hugely different from an 11/83 anyway. The main benefits are that memory access by the CPU can happen without contention from Qbus (I think it can even be done sortof in parallel), and of course, the speed of main memory is fast enough that it's all about the CPU speed limit.

Any OS should have a pretty marginal overhead with interrupts and other activities going on, unless you are actually running something else actively at the same time.

And the FPJ11 is really just an FPA. It accelerates FP. The J11 does FP instructions with or without the accelerator. It just runs faster with. :)
As opposed to the FPF11 (was that the name?). Without that, the F11 cannot do FP instructions at all.

And sadly, yes, the Pro-380, while nice in some ways, really is sad in that it runs the CPU at 10 MHz, and also P/OS don't even allow you to use split I/D space, or supervisor mode. A machine with such potential but such a failure. :(
And obviously, the CPU can run faster, but as I heard things, some support chips can't, which is why the -380 only is running at 10 Mhz.
 
Also, as a comparison. Run on an 11/93 with M+:
.swa run pi2
SWATCH -- Timing : RUN PI2
PLEASE WAIT WHILE I COMPUTE THE VALUE OF PI...
AFTER 262144. ITERATIONS, I HAVE DETERMINED
PI IS APPROXIMATELY 3.141592653589796
SWATCH -- Timing finished.

End : 17:27:29.08
Start : 17:27:11.38
-----------
00:00:17.70
-----------

Copyright (C) 1988 XDT Computer Consultants.

.
Just copied the source over, compiled with F77, no switches, and linked with F77FCS.

So, 17s, compared to an 11/83 at about 22s.
 
Also, as a comparison. Run on an 11/93 with M+:

Just copied the source over, compiled with F77, no switches, and linked with F77FCS.

So, 17s, compared to an 11/83 at about 22s.
Thanks Johnny! I'm now curious as to the results on Hunta's 24mhz nightmare fuel system.

Now I have to put the PMI memory into the 83 and see how close it can get to a 93.
:)

In terms of the 380, yeah it's a slug. But according to my test results at 2 minutes, that would make it six times *slower* than the 11/83. Maybe the lack of the FPJ11 makes more of a difference on Fortran/77.

Which means it's time to fire up the 11/73+ with PMI memory but WITHOUT FPP :-) Off to find another ethernet cable.....

(And I really should update the tcp/ip software too)
 
Hm, this is also interesting:
11/73+ CPU, 4mb Clearpoint PMI memory, RD54, no FPJ11, RSX11M+ 4.6, Fortran 77 compiler
$ @PI
$ SHOW TIME
13:15:22 17-NOV-2025
$ RUN PI
PLEASE WAIT WHILE I COMPUTE THE VALUE OF PI...
AFTER 262144. ITERATIONS I HAVE DETERMINED
PI IS APPROXIMATELY 3.141592653589796
$ SHOW TIME
13:16:43 17-NOV-2025

So the 11/73 runs it in at 1 minute, 21 seconds. A lot slower than the 83 and the extra clock is not making this big a leap.

Verdict: The FPJ111 chip makes a big difference over the microcode in the KDJ11 chip. Man I can see why they built it.
Assertion: Fortran 4 isn't optimizing much for the FPJ11. Fortran 77 is for the win.
Verdict: The Pro/380 is a slug, but that's partially due to the lack of FPJ11 as well as the slow clock speeds.

Ok, back to work before I drag out a pdp11/23+FPF11 to see how Fortran 77 runs on that.

(Edit: Also need to adjust NTPD for Eastern Standard time, not daylight)
 
Well... We meet the nightmare :)
M8190, 24MHz J-11, FP, ClearPoint DCME-Q4E-F + RSX-11M-Plus 4.6
Code:
>PIP /LI
 
 
Directory ZB0:[10,1]
17-NOV-2025 21:56
 
PI.FTN;1            2.         17-NOV-2025 21:53
PI.FOR;1            2.         17-NOV-2025 21:52
PI.OBJ;1            2.         17-NOV-2025 21:53
PI.TSK;1            43.     C  17-NOV-2025 21:55
PI.CMD;1            1.         17-NOV-2025 21:56
 
Total of 50./50. blocks in 5. files
 
>@PI
>TIM
21:56:10 17-NOV-2025
>RUN PI
PLEASE WAIT WHILE I COMPUTE THE VALUE OF PI...
AFTER  262144. ITERATIONS, I HAVE DETERMINED
PI IS APPROXIMATELY 3.141592653589796
>TIM
21:56:24 17-NOV-2025
>@ <EOF>
About 14 seconds :)
 
Hm, this is also interesting:
11/73+ CPU, 4mb Clearpoint PMI memory, RD54, no FPJ11, RSX11M+ 4.6, Fortran 77 compiler
$ @PI
$ SHOW TIME
13:15:22 17-NOV-2025
$ RUN PI
PLEASE WAIT WHILE I COMPUTE THE VALUE OF PI...
AFTER 262144. ITERATIONS I HAVE DETERMINED
PI IS APPROXIMATELY 3.141592653589796
$ SHOW TIME
13:16:43 17-NOV-2025

So the 11/73 runs it in at 1 minute, 21 seconds. A lot slower than the 83 and the extra clock is not making this big a leap.

Verdict: The FPJ111 chip makes a big difference over the microcode in the KDJ11 chip. Man I can see why they built it.
Assertion: Fortran 4 isn't optimizing much for the FPJ11. Fortran 77 is for the win.
Verdict: The Pro/380 is a slug, but that's partially due to the lack of FPJ11 as well as the slow clock speeds.

Ok, back to work before I drag out a pdp11/23+FPF11 to see how Fortran 77 runs on that.

(Edit: Also need to adjust NTPD for Eastern Standard time, not daylight)
If you have PMI memory, the machine is technically an 11/83, and not an 11/73. That is really what differentiates between the two models. Not clock frequency, but PMI memory.
No FP acceleration really makes a difference, yes.

As for the 11/23+. There are two different FP options for it. One is a chip, the other a full board. My understanding is that the full board FP is the fastest, but I've never tested that.

And speaking of daylight saving. In addition to updating TCP/IP, you should install the DST package to get automatic switching between DST and not in RSX. ;)
 
Well... We meet the nightmare :)
M8190, 24MHz J-11, FP, ClearPoint DCME-Q4E-F + RSX-11M-Plus 4.6
Code:
>PIP /LI
 
 
Directory ZB0:[10,1]
17-NOV-2025 21:56
 
PI.FTN;1            2.         17-NOV-2025 21:53
PI.FOR;1            2.         17-NOV-2025 21:52
PI.OBJ;1            2.         17-NOV-2025 21:53
PI.TSK;1            43.     C  17-NOV-2025 21:55
PI.CMD;1            1.         17-NOV-2025 21:56
 
Total of 50./50. blocks in 5. files
 
>@PI
>TIM
21:56:10 17-NOV-2025
>RUN PI
PLEASE WAIT WHILE I COMPUTE THE VALUE OF PI...
AFTER  262144. ITERATIONS, I HAVE DETERMINED
PI IS APPROXIMATELY 3.141592653589796
>TIM
21:56:24 17-NOV-2025
>@ <EOF>
About 14 seconds :)
Roughly following the clock frequency of the machine. Which is as it should be.
 
If you have PMI memory, the machine is technically an 11/83, and not an 11/73. That is really what differentiates between the two models. Not clock frequency, but PMI memory.
No FP acceleration really makes a difference, yes.
Ok, 83's are weird. Some were 11/73's with PMI, later ones had the 18mhz CPU. But I don't think you can upgrade a 73 board to an 83 board by changing the clock speed (maybe you can, see Hunta there)

My systems are kind of hand rolled these days after 30 years of tweaks. That said I'd rather have an 18mhz CPU with normal memory than a 15mhz CPU with PMI memory.
As for the 11/23+. There are two different FP options for it. One is a chip, the other a full board. My understanding is that the full board FP is the fastest, but I've never tested that.

And speaking of daylight saving. In addition to updating TCP/IP, you should install the DST package to get automatic switching between DST and not in RSX. ;)
Oh wow, another super cool program! Thanks, I'll do that over the weekend....

C
 
Back
Top