I'm doing load testing with web tests. The web tests that the load test uses require going through a couple different pages to get to the "important/interesting" page. Every time I re-run the load test, I have to drill into the counters and find the "avg. page time" for the specific page I'm interested in.
Two questions:
1. Is there a way to "save" the counters I'm interested in so that they redisplay automatically each time I rerun the test
2. The stats being collected appear to have many holes where no data was collected. For example, the avg page time was collected at 15, 20, 25 and 40 seconds, but not at 30 or 35. What factors dictate when the stats are actually collected
Thanks in advance.
Mark
Load Testing - Counters
Lence
ewebull
DuRob
While running the load test, I've double clicked on the test in progress and viewing the graphs/counters there. After the test completes, I close this tab/window. Re-running the test always results in the counters defaulting back to the original list.
My gut tells me to try and "save" the window ... but there does not appear to be a save feature
Thanks in advance for clarifying.
Mark
Vorda
Right, so if no tests complete in the time the load test is running the page and transaction counters will not be reported. We realize this is a problem and will fix it our next version.
Ed.
BigAlz
Cloakas
1. The visible counters are saved automatically into the .suo file, I believe, when you close the load test monitor. Note that this data is keyed on the load test id and the controller name, so you'll get different data if you change either one. Leaving a load test monitor tab open is by far the most common cause of the counters not being saved.
2. Gaps in the graph indicate the controller or the target machines are too busy to collect/provide performance counters. If you're running locally, you may need to dial back the load a bit. If you're running a controller, make sure the controller isn't also running the agent service as that will cause it to get too busy. A typical configuration is a controller machine running SQL for the load test database and separate agent machines running only the agent service.
I hope this helps,
Josh
Carl
You are experiencing a bug that will be fixed in a future update. Unfortunately, there is no work around other than re-selecting the page counters you want to view for each run.
As Josh mentioned, the load test monitor's state (graphs, counters on graph, options, etc) is saved automatically when the monitor is closed. The problem you are seeing is related to individual LoadTest:Page and LoadTest:Request counters.
An individual LoadTest:Page or LoadTest:Request counter instance has a base name (such as default.aspx) and an associated numeric identifier which maps to a set of metadata about the page or request (which test is it included in, what scenario, full URL, etc).
The base name and associated metadata identifier for a page/request counter is being persisted in the .suo file. However, it is not guaranteed that the same identifiers will be associated for page/request counters from one run to another. Thus, the selected page or request counters may not be matched up properly on successive runs.
Note, the "overall" page/request counters and all non-load test counters will not have this problem and will be saved and reloaded properly on successive runs.
Sorry for the inconvenience this is causing.
Rick