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 Size
obj_vax/ 512
build_hyperspi$agent.com 1K
build_hyperspi.com 2K
examplegraph.gif 4K
gifspi.c 15K
hyperspi$agent.c 46K
hyperspi$agent.com 1K
hyperspi.c 126K
hyperspi.h 2K
hyperspi.html 6K
hyperspi_example.gif 38K
interpretingspi.html 3K
plotspi.c 11K
readme.html 3K
spidef.h 32K