These are 'easter eggs', in the process of gathering information, we
are at first getting as lot more than you can sanely display (or are prob
relevant). So we deal with trying to determine what metrics are actually
useful for displaying. 

In doing so, we end up with other graphs for some of the tests which
anyone can bring up by adding the number to the end of the URL.

a quick explanation

vmstat          system, user, idle time
vmstat2         load average and system, user, idle time together.  works
                OK until your LA spikes real high
vmstat3         interrupts and context switches
vmstat4         LINUX ONLY memory:swap in, swap out
vmstat5         LINUX ONLY disk io: blocks in, blocks out
vmstat6         SOLARIS ONLY memory:size of free list, swap avail.
vmstat7         SOLARIS ONLY memory:page reclaims, minor faults
vmstat8         SOLARIS ONLY memory:pages in, pages out
vmstat9         SOLARIS ONLY memory:scan rate

 
netstat         attempt to chart TCP connection activity.
netstat1        attempt to chart UDP activity
netstat2        attempt to chart TCP thoroughput for LINUX this is
                WRONG because netstat -s does not output in bytes but segments