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.
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.
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 has been developed and tested on 6.n systems. I have no idea what will happen on under 7.n.