Opening LoadTest results is very slow. What might cause this behaviour?
This issue can be caused by the excessive use of custom timers in the script.
For example, dynamic timer names may have been used causing an excessive amount of timers to be collected, or the Active Profile setting "Add transaction name and an identifier to measure names" has been activated under SETTINGS | ACTIVE PROFILE | RESULTS | GENERAL, resulting in more timers than expected. These are the most common reasons why excessive timers might be generated.
To determine if this is the reason, review the results file when it opens. If there are a very large number of timers reported it’s expected that the results will take some time to open. This can be prevented by modifying the script to make sure excessive information is not collected.
If more detail than the default is required, there is the possibility of using the Raw data capture option which can be found under SETTINGS | ACTIVE PROFILE | RESULTS | TIME SERIES. Further details on this option can be found under the heading “Raw Measure Data Capturing” in the Silk Performer Help file, and is also discussed in this blog post: Raw Measure Data Capturing
It is also possible to enable this feature for specific measures using the MeasureCollectRawData Function.