HyperSPI-plus-plus generates VMS System Performance Information HTML documents. It can profile, complete with graphics, fundamental system performance indicators as CPU usage, memory usage, IO values. It works extremely well. Here are examples of its output; CPU Usage and Memory usage, along with information on its capabilities.
2011 Note: HyperSPI++ has received scant attention in the last decade. This note brings it up to building in more modern Alpha and in particular Itanium environments, and adds network interface data. It has not been extensively tested in any; YMMV.
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it under the
conditions of the original license, with some portions available under the GNU
GENERAL PUBLIC LICENSE, version 2.
Copyrights exist on parts of the charting library and may have different distibution licenses. All are provided "as-is" and are freely available for unrestricted use.
HyperSPI++ comprises two distinct applications.
Quick links to selected reports can be useful:
Graphical <A HREF="/cgi-bin/hyperspi">performance information</A> for selected VMS compute servers. <BR>Since 7am today: <A HREF="/cgi-bin/hyperspi?list_node=SYSTEM&period=until_now&cpu=yes&memory=yes&hard_faults=yes&do=page">SYSTEM</A> <BR>Since yesterday: <A HREF="/cgi-bin/hyperspi?list_node=SYSTEM&period=since_yesterday&cpu=yes&memory=yes&hard_faults=yes&do=page">SYSTEM</A> <BR>The last week: <A HREF="/cgi-bin/hyperspi?list_node=SYSTEM&period=7&cpu=yes&memory=yes&hard_faults=yes&do=page">SYSTEM</A>
Note that the startup and run-time procedures WILL require some modification.
The collection agent be must started up on all nodes for which information is required. The logical name HYPERSPI$DATA locates where the data is recorded and read from. It is important this data is cleaned-up occasionally. It uses approximately 394 blocks (~200kB) per day per system. The HYPERSPIXX$STARTUP.COM procedure provides an example startup.
This version of hyperSPI++ (v3.0) has not been extensively deployed and so in some respects the build should be considered field test! It does compile cleanly under "HP C V7.3-009 on OpenVMS Alpha V8.3" and "HP C V7.1-011 on OpenVMS IA64 V8.3-1H1". Outside of these your milage may vary.
$ SET DEFAULT device:[dir] $ UNZIP -V location:HYPERSPIXXnnn.ZIP $ SET DEFAULT [.HYPERSPIXX] $ @BUILD_HYPERSPIXX $ @BUILD_HYPERSPIXX$AGENT
Some installation and configuration will be required for the data collection agent and for the presentation script. See "Description" above.
This version has been tested under WASD. It should also operate under OSU (DECthreads) and VMS Apache.
HyperSPI++ seems to be fairly sensitive to the EXE$GETSPI()
system call (probably not unreasonably) and may need at-the-least relinking
depending on the exact VMS version. It was originally developed and tested on
V6.n systems, then with V7.1 and V7.2, and most recently (after a decade
senescence) on VMS V8.3 Alpha and Itanium. After operating system
upgrades the HYPERSPIXX$AGENT may required a relink
(
Problem reports, bugfixes, notices of usage should be provided to Jean-François Piéronne (jf.pieronne@gmail.com) in the first instance.
This package is available for download from