Using Session Hunter

  1. Run SessionHunter.exe
  2. On startup, it should prompt you for a SQL connection. This should point to the ASP state database you wish to analyze.
    • Note: This has been written intending to be used on live production ASPState databases. Since it is still in Alpha state, I recommend you take a copy of your session database, copy it to another SQL server and then run it there until it has gained more maturity.
  3. If the connection succeeds, it should return a list (defaults to 20) of the largest sessions. If you click on any session, it will return a list of all items in that session.
  4. If it cannot resolve the type, the References button will blink and it will display it as “Unknown type”. See Resolving References for guidance. It should be noted that performance of Session Hunter is significantly degraded when it cannot resolve references. In one test, processing 5000 session items that could not be resolved took 75 seconds, while it only took 8 seconds to process when it could resolve the references.
  5. Now that you have your largest session and what they contain, you should be able to look through your code and track down the biggest offenders and optimize them.

Additional Pages

  1. Settings - See this page if you need help understanding the settings tab
  2. Troubleshooting - See this page for a list of ways to troubleshoot the tool.
  3. Screenshots - Screenshots of some of the screens in Session Hunter

Last edited Feb 2, 2013 at 9:29 PM by repuust, version 13


No comments yet.