Testing Propel Accelerator

Issues & Strategies for Accurate Testing

Now that you know what Propel Accelerator does, you probably want to start testing. The following are the key issues that must be considered when benchmarking.

ISSUE STRATEGIES

Page load times may vary for reasons that have nothing to do with Propel Accelerator.

  • Network and server traffic variations
  • Rotating and customized content on test pages
  • Hardware and modem connection variations
  • Use averages and percentiles to summarize results
  • Do parallel testing on multiple matched machines
  • Verify that line quality and modem speed match across all tests
  • Take many sample timings for each URL in each test configuration

Acceleration can vary depending on page type and content type

  • Graphics heavy vs. text heavy pages
  • Number of ads on page
  • Dynamic vs. static pages
  • Evaluate acceleration for different page types separately

Acceleration can vary depending on surfing pattern

  • First time visit to page
  • Return to page later on the same day
  • Return to page a day or two later
  • Evaluate acceleration separately for first time visits, repeat visits on same day, and next day visits

Propel Accelerator - Testing Procedures Guide (PDF)

Getting Started With Your Testing

Please follow the Do's & Don'ts listed below to ensure "true" data is obtained during testing.

  1. Don't use bandwidth meters! Bandwidth meters won't help since they simply measure raw data rates. Web accelerators don't improve data rates; rather they reduce the amount of data transferred, which results in faster page display time.
  2. Don't compare accelerator-reported bandwidth estimates because each company is estimating, and there's no standardization.
  3. Do use multiple, matched machines.
  4. Do use Stopwatch (numion.com) or PropelRT (shown below) to gather data. (Please contact Propel ensure you are using the correct tools for evaluation.)

Performance

The Propel Experience

Below is a simplified example of how Propel Accelerator delivers its amazing performance. Please note that the setting chosen for the final graphics quality will affect the ultimate level of acceleration received.

Initial Page Visit

The following will occur upon the initial Web page visit:

  • The request for the Web page is automatically routed by the Propel Client to the Propel Network.
  • The Propel Network retrieves the requested Web page from the Website.
  • Elements of the Web page (both text and graphics) are encoded and cached before being sent to your PC / Mac.
  • These page elements are then decoded by the Propel Client, and assembled and delivered to the Web browser.

Subsequent Page Visits

The following will occur upon subsequent Web page visits:

  • Your request for the Web page is automatically routed by the Propel Client to the Propel Network.
  • The Propel Network retrieves the requested Web page from the Website. Having identified the page elements that had previously been retrieved in a prior visit, the Propel Network only compresses and transmits those components that have changed.
  • Data already stored on your PC / Mac - plus any new decoded page elements - are assembled locally by the Propel Client and delivered to the Web browser.

Results

The following chart reflects the performance results for Propel Accelerator on various Website types:

The following chart reflects the performance results for Propel Accelerator on various connection speeds: