This application generates VMS System Performance Information HTML documents. Coupled with 'HyperSpi$agent.c', the data-collection application, it can profile, complete with graphics, fundamental system performance indicators as CPU usage, memory usage, IO values. It works extremely well. This is an example of the output and some 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.
HyperSPI comprises two distinct applications.
A mapping rule should be included in the HTTPD$MAP configuration file:
script /hyperspi* /cgi-bin/hyperspi*
Quick links to selected reports can be useful:
Graphical <A HREF="/HyperSpi">performance information</A> for selected VMS compute servers. <BR>Since 7am today: <A HREF="/HyperSpi?list_node=SYSTEM&period=until_now&cpu=yes&memory=yes&hard_faults=yes&do=page">SYSTEM</A> <BR>Since yesterday: <A HREF="/HyperSpi?list_node=SYSTEM&period=since_yesterday&cpu=yes&memory=yes&hard_faults=yes&do=page">SYSTEM</A> <BR>The last week: <A HREF="/HyperSpi?list_node=SYSTEM&period=7&cpu=yes&memory=yes&hard_faults=yes&do=page">SYSTEM</A>
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 140 blocks (70Kbytes) per day per system. There is an example startup for the data collection agent. To start the data collection agent up during system startup add
$ DEFINE /NOLOG /SYSTEM /EXEC HYPERSPI$DATA device:[directory] $ @WASD_ROOT:[SRC.HYPERSPI]HYPERSPI$AGENT STARTUPat an appropriate place in the system or HTTP server startup procedures.
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 developed and tested on
6.n systems, and later was reworked on V8.3. After operating
system upgrades the HYPERSPI$AGENT may required a relink
(
Name Revised Size Description
obj_vax/ 2-May-2014 14:23 512 subdirectory build_hyperspi$agent.com 2-May-2014 14:23 1,889 DCL procedure build_hyperspi.com 2-May-2014 14:23 2,133 DCL procedure examplegraph.gif 2-May-2014 14:23 4,625 GIF image gifspi.c 2-May-2014 14:23 15,491 C source hyperspi$agent.c 2-May-2014 14:23 47,883 C source hyperspi$agent.com 2-May-2014 14:23 1,112 DCL procedure hyperspi.c 2-May-2014 14:23 129,628 C source hyperspi.h 2-May-2014 14:23 2,532 C header hyperspi.html 2-May-2014 14:23 6,705 "HyperSPI - Help" hyperspi_example.gif 2-May-2014 14:23 39,019 GIF image interpretingspi.html 2-May-2014 14:23 3,885 "HyperSPI - Performance Assessment Guidelines" plotspi.c 2-May-2014 14:23 12,206 C source readme.html 2-May-2014 14:23 4,001 "HyperSPI readme" spidef.h 2-May-2014 14:23 32,885 C header