The recent article, "Monitor de Sistema (Re)visited", was based on data
collected running VMS on the same modest X86 desktop previously reported.

  Dell Optiplex 9020 4-core i7 3.4Ghz 16GB Win 10 Pro 22H2
  innotek GmbH VirtualBox with 3 CPU and 3840MB running VMS V9.2-1
  Approximate System VUPs Rating : 248.3 ( min: 246.4 max: 250.6 )
  VSI TCP/IP Services for OpenVMS x86_64 Version 66.0
  VSI C X7.4-785 (GEM 50X65) on OpenVMS x86_64 V9.2-1

The article was about MonDeSi, not X86 VMS performance; however...

The OWASP ZAP scanner exercising MonDeSi was running on a 3.2 GHz 6-Core
Intel Core i7, 32 GB, macOS 14.0, over a 1Gbps LAN, occupying multiple cores
at an overall ~25% utilisation.  See attachment macOS_stats.png image.
  
The 4-core i7 3.4Ghz 16GB Dell still managed to keep those three VMS CPUs
performing at full(ish) capacity, shown by the attachment MonDeSi_clip.png
image (without a major update, VMS Kernel mode is still notable), while
basically humming along itself at 40% CPU utilisation (not sure exactly what
this suggests about VMS/hypervisor efficiency/utilisation), as indicated by
the TaskManager_CPU.png image.

The network utilisation, also shown by MonDeSi_clip.png, maxed-out at
3.87MBps (megabytes), or roughly 300.7 Mbps (megabits), confirmed by the peak
in the attached TaskManager_ethernet.png image.  This across a 1Gbps real LAN
between two systems (OK, both connected to the same switch).

Not too shabby for a pre-loved AU$300 commodity desktop.

PPS. The peak network utilisation of 300Mbps, in fact over 500Mbps in other
testing under X86 VMS, prompted a bump from 32 to 64 bit storage for the
MonDeSi bits per second datum ... who knows what 10GbE will bring.

This item is one of a collection at
https://wasd.vsm.com.au/other/#occasional