Related Content

Performance Troubleshooting Steps

Posted by Osvel Legon on November 2, 2011
0 people like this tutorial

Developer Testing and Performance Verifications

  • Prior to running a full load test, all pages need to be reviewed for performance in development mode
  • Put site in Dev Mode
  • Enable TRACE="TRUE" on the templates
  • Load each page on the site one by one and review the overall load time numbers in the trace info at the bottom of the page. If your Dev Mode version of the page takes more than 5 seconds in the trace report YOU MUST OPTIMIZE. If the trace time is over 10 seconds we have MAJOR ISSUES and cannot launch in that state.
  • Optimization should follow the troubleshooting steps below in the troubleshooting section.

Troubleshooting Performance Issues

Typically you need to create a clone of the site and Agility instance as per above

  • Enable TRACE="TRUE" on the template of the offending page(s)
  • Check the page template first without any published modules. We need to confirm that the problems are not in the template itself
  • Review the Trace for where things are running slow (e.g. onInit, PreRender, etc.)
  • Then go into each module and test by using a "return" to return out early until you find the piece of code that is causing the slowdown
  • Address the slow code and double check that the issue you have fixed is not used or occurring anywhere else on the site.
  • Re-test using Trace until you are sub 5 seconds
  • You may need to run another single user/single thread load test across the site to guarantee the issue has been addressed. Developer machines are pretty fast with a lot of RAM, but client servers vary widely. STAGING is a pretty average machine so we need to make sure things are sub 5 seconds on STAGING.

Ultimately if pages render sub 5 seconds in dev mode on STAGING with long lists of test content we should not be seeing performance issues once launched.

Add a Comment



Log in with your Agility username and password or
register for the site

Log In