| || |
Does wlGlobals.myVar has the scope for all the generators with the same agenda everywhere??????????????????
Re: Does wlGlobals.myVar...
No: wlGlobals is common to all virtual clients within a single load generator (and, with spawning, is only global to each spawned load generator).
WebLoad 4.5 introduces a new concept where you can set and manage "true" global variables across load generators and machines; check the manuals for wlSystemGlobal and wlGeneratorGlobal objects. Be warned, however, that since you will be effectively synchonizing across multiple machines using these objects will cause a performance hit.
If you're looking for help for your arrival rate issue you might try setting up one load genertator on 5 different machines (for simplicity). If you expect your query to take under 10s under load then you can set up 10 VCs (one per second) on each load generator.
You sync all the VC's in InitClient, and then have them start at 1 second second intervals, taking note of the time they start so that they can delay the appropriate time (in this case a max 10s) once the query completes.
This way each machine will start only one new round per second, with 5 machines and a little scripting you can get your arrival rate sorted out without resortng to globals. The technique will, of course, fail if your query takes longer than you expect. Of course, you can set the globa performance figure in the dialogs to cause an error (transaction failure) when this happens. or throw the appropriate error message in your agenda when the elapsed time for the query exceeds your target amount.
Hope this helps,