CPU usage - related to parsing?
I've just started using WebLoad 5.0 and I'm seeing dramatic CPU usage. My script is pretty simple - it picks a random path through about 5 pages of links, fills data in a form, and submits it to complete a registration process. When I ran the script the first time I started at 1 user and ramped up by 1 every 2 minutes. by the time i reached 15 users i was seeing a sawtooth shape on the CPU usage in TaskManager (remember your oscilliscope in electronics class?) that was using 100% of CPU for a few seconds and dropping to almost zero, then spiking again. It started off gradual, then the duration of the spike increased until usage was solid at 100%. This happened simultaneously on the console and the generator (correlating spikes). Console is 1.8GHz P4 1GB RAM, generator is Dual 1.1GHz P3, 2GB RAM. Same thing happens if I start at 20 users and go up by 5 every 2 minutes - after about 60 users, usage is spiking to 100%. My script uses: wlGlobals.SaveSource = "Yes" and wlGlobals.ParseLinks = "Yes" as well as: pagesource.search(pattern) and document.links.length to be able to parse links from a page and then randomly pick one (this happens on about 4 pages in a row). Radview tech support suggested that parsing can be resource intensive. Since this is what I need to do, is there a better way to do this? Or is WebLoad not the right tool for this? Thanks.
I love deadlines. I like the whooshing sound they make as they fly by.
Re: CPU usage - related to parsing?
Parsing in WebLoad can be resource intensive. One thing you might try, if you don't need to parse every single page is to use wlHttp instead of wlGlobals. For instance, when using SaveSource, instead of turning it on for the entire script, simply set only for the pages where you really need the source for your patterns. Use wlHttp.SaveSource for these 4 pages only. You don't need SaveSource enabled for all pages unless you are parsing all of them with a pattern. Normally when there is significant parsing enabled, this takes a toll on the load generator, but not necessarily the console. Are you running any other apps at the same time? Do all of your scripts cause CPU spikes, or just ones where parsing is occuring? Hope this helps.