Fail: Check saving session information into DB
I'm using LoadRunner 8.0. When I check saving session information into database. I see result which is not stable. System save 1 record, 2 records or 3 records for a session. I just check very simple: check share balance in saving session information (using many server to store session information). System save 1 record/1 session if I check by manual. But I simulate 1000 Vuser = 1000 session by LoadRunner 8.0. System save more than 1000 records. I can't understand this problem. Please help me what working mechanism of LoadRunner? Why in a action, it can produce many session?
"Name=submit.x", "Value=50", ENDITEM,
"Name=submit.y", "Value=9", ENDITEM,
Dang Hong Phu, Viet Nam, Vinagame company
Re: Fail: Check saving session information into DB
Yes, a 1000 LoadRunner virtual users will create a 1000 session handles to a server application. This is no different than a 1000 physical users using a 1000 session handles to the server applications. If each session saves a single record, then it is entirely plausible that either a 1000 user population of physical or virtual users will produce a 1000 records.
I guess I am missing the question....perhaps you could rephrase.....(!?)
Replace ineffective offshore contracts, LoadRunnerByTheHour
. Starting @ $19.95/hr USD.
Put us to the test, skilled expertise is less expensive than you might imagine.
Twitter: @LoadRunnerBTH @PerfBytes