WebStress Academy Bill McCormick Global Summit 2011

WebStress Academy AgendaAgenda –Introduce the tool –Record a script –Edit the script –Randomization –Define a test with more then one or more scripts –Execute a benchmark run –Validate the run

What is WebStress A utility being shipped as part of the product in 2011A utility being shipped as part of the product in 2011 A tool that allows for recording http traffic between any client and server that supports running thru a proxyA tool that allows for recording http traffic between any client and server that supports running thru a proxy Allows for customizing and randomizing the data being utilizied from a given recorded base scriptAllows for customizing and randomizing the data being utilizied from a given recorded base script Can play back multiple recordings simultaneously to simulate load and verify results, including performance metricsCan play back multiple recordings simultaneously to simulate load and verify results, including performance metrics

Why WebStress? TrakCare performance evaluations required for certain bidsTrakCare performance evaluations required for certain bids –Brisbane –Edinburgh LoadRunner and other tools for this can be very expensiveLoadRunner and other tools for this can be very expensive Managing CSP / Zen based applications requires a few little tricks to benchmark correctlyManaging CSP / Zen based applications requires a few little tricks to benchmark correctly Has been used in dozens of benchmarks since 2002Has been used in dozens of benchmarks since 2002

Some core concepts ControllerController –Manages the playback of a test and gathers results GeneratorGenerator –Machine that is executing the script and randomization logic during playback. Can be same machine as controller WebServerWebServer –The URL that the application is running over. In the case of a Cache system it also allows us to connect to the server App ServerApp Server –The actual database being used by the test under Cache

Continued NoEncrypt FlagNoEncrypt Flag –Sets the flag that allows benchmark recordings and playback to work on CSP / Zen based solutions No DelayNo Delay –For non page content ignore recorded delays –js, html, css, jpg etc No ResultsNo Results –For non page content ignore results –js, html, css, jpg simulates cacheing

Continued ScriptsScripts –A collection of http requests that from a UI perspective represent a “transaction” or “workflow” TestsTests –A collection of scripts that when combined represent a “server usage profile” Save Page SourceSave Page Source –For verification purposes this will loop over a script and save the returned page content to a local directory

Recording WebStress has a facility that launches a listener on a defined portWebStress has a facility that launches a listener on a defined port A browser for example can be configured to use this port as a proxy and we capture the outputA browser for example can be configured to use this port as a proxy and we capture the output We will offer to set the no encrypt flag for a given cache service when the listener is launchedWe will offer to set the no encrypt flag for a given cache service when the listener is launched The recorder also generates a routine for providing randomization logicThe recorder also generates a routine for providing randomization logic Exercise 1Exercise 1

Customizing a Script Once a recording is completed we can edit it to change settings and values or completely randomize data being usedOnce a recording is completed we can edit it to change settings and values or completely randomize data being used –Parameters These are name value pairs that were submitted via httpThese are name value pairs that were submitted via http –Http Headers This is the information your browser added to the http request when it was POSTed or GETThis is the information your browser added to the http request when it was POSTed or GET –URLs These are the individual http requests captured. They can be removed or manually addedThese are the individual http requests captured. They can be removed or manually added Exercise 2Exercise 2

Creating a Test Controls the playback of the various scriptsControls the playback of the various scripts –Scheduled –Start now –Run time –Warm up / Cool down –Using Delays –Page Source

Tests Continued Adding ScriptsAdding Scripts –Select a script –Choose a Web Server –Define the rate SessionsSessions ProcessesProcesses –URL Loopback –Target Repeat as neededRepeat as needed

Tests Continued Adding ScriptsAdding Scripts –Select a script –Choose a Web Server –Define the rate SessionsSessions ProcessesProcesses –URL Loopback –Target Repeat as neededRepeat as needed Exercise 3Exercise 3

Running a Benchmark Preparing a TestPreparing a Test –Starts the processes on the Generator –Starts the controller’s listener that drives the generators and collects the data Run the TestRun the Test –The Controller sends the start signal to the generators –Results are ignored for the duration of the “warm up” –Live results display on this page After the testAfter the test –Results are processed –Jobs Halted

Continued Exercise 4Exercise 4

WebStress Summary Runs on Runs on Can be used against any http based applicationCan be used against any http based application Https not supported at this timeHttps not supported at this time Keep Alive must be disabled during recordingKeep Alive must be disabled during recording

WebStress Academy Thank youThank you Bill McCormick - McCormick - Pat McGibbon - McGibbon - Iain Bray - Lead developerIain Bray - Lead developer

WebStress Academy Bill McCormick Global Summit 2011