loadrunner Need help of ASP.NET Viewstart auto...

  • Thread starter Muzammil Husain Shaikh
  • Start date
  • perf-test.com need your contributions to build up a strong repository of performance engineering resources.

M

Muzammil Husain Shaikh

Guest
Need help of ASP.NET Viewstart auto corrletion, I am able to find LB and RB, but due to sooo much of data in script, not able to find out what to replace with "Correlated_Varaible" (c_ViewStart)
 
Check: VuGen > Record > Recording Options > Correlations > Rules There are built-in correlation rules for ASP.NET, including "VIEWSTATE". Just use them
 
This podcast may help you. http://www.perfbytes.com/dynamic-data-correlation Keep in mind that several viewstates may be open and active at once. IT is almost never that you have a pure sequence from one to the next. At some point expect a break in the sequence resulting in one to two sets of state management variables being active at any given point. Recording multiple times should help to identify what's changing and the sequencing
 
And, by the way, forget "auto corrletion," move to manual correlation. There are a number of reasons for this, but the core of which is that quite often the match buffer of LoadRunner is too small for the large viewstates represented to effectively match the standardized left boundary and right boundary condition when applying the rule. As a result the automagical correlation engine does not identify an item when needs to be addressed and instead you need to identify this item manually. It is an axiom that if a business process code developer is reliant upon auto correlation to handle all of the dynamic components that the code under review will manifest a piece of dynamic data which is unhandled by the auto correlation rules and the developer will be left without recourse on any method to "fix the correlation." I am assuming that your hiring organization has provided you with standardized training on the tool. If you have a weakness in the area of manual correlation then you will want to review the chapters in the (assumed HP standardized ) training material related to manual correlation.
 
Also get to know and LOVE the newer regular expression version of the correlation functions. Wish I had them back in 1999!! Yes, for normal .net asp(x) apps the built in viewstate definition when turned on for recording works pretty well right out of the box.
 
James, we (LoadRunner R&D) were surprised to hear about the buffer size limitation. We've just tried a sample with ~500KB ViewState parameter and correlation rule handled it successfully. We provided new set of correlation rules for ASP.NET in LR 11.52 and all known ViewState cases should be handled automatically…
 
I regularly see multi megabyte view states, even as large as 16mb one time with an entire access db in state! As view states get ugly large the ability of loadrunner to find that rb in the pattern buffer drops off and you wind up back at manual
 
I'll check my archive for samples. I'll also need to check with clients before sharing. I should note, I do not consider this a defect but a design limitation based upon reasonable assumptions associated with returned page size. In a script you can tune the buffer size higher with web_set_max_html_param_len() but I haven't found any way to tune the size of the default match buffer for auto correlation. I am all eyes of you have a tuning parameter for an initialization file!