For example: with Stingray PageSpeed enabled you can now measure the effects of increasing the initial congestion window on your Ethernet interface, or see the improvements made by enabling Aptimizer on your website:
This information can then be pushed out to a log file or other event target via the alerting system, or simply viewed in the PageSpeed UI:
To deploy PageSpeed on your Traffic Manager you will need to upload the components contained in the partial backup. If you are running Stingray 8.1 then you should be able to import the backup directly in the Stingray admin UI. If not you can upload/copy the files to your Traffic Manager manually. PageSpeed consists of the following configuration items:
The two rules are the TrafficScript rules and these will need to be enabled as a request and response rule on the Virtual Server for which you want to enable PageSpeed.
The extra files should be uploaded to the extra files catalog. The psmap.html and psdata.html are html templates for the PageSpeed UI, and the blank.gif is the blank which terminates the rendering measurement.
The events/action files enable PageSpeed to log to a simple logfile via the Stingray alerting system.
The PageSpeed configuration is held in the PageSpeedRequest TrafficScript rule. There are a number of parameters which need to be set:
The pages to track
Modify Cache header
Enable logging via PageSpeed event target
Enable the PageSpeed UI
The userassword for HTTP Basic Auth in PageSpeed UI
max requests to show in UI
$maxGreen, $maxRed, $maxAmber
Set the colouring on the PageSpeed map page
The lat and lon of the DCs
DemoMode enables spoofing in the rule and adds artificial delay to requests based on proximity to the DC.
KM/Second used for artificial delay in demoMode
Refresh period for map page in the UI
Use Google maps in the UI?
Supply a bing API key if you want to use Bing maps in the PageSpeed UI
The most important setting is the “pages” hash, which should be set with the list of pages on your site which you want to track. You should also change the password for the PageSpeed UI if you keep it enabled, and obviously demoMode should be set to false on all production TrafficManagers.
Finally. To access the PageSpeed map and data pages, simply point your browser at: http://<yoursite>/PageSpeed/UI