Is anyone familiar with the browser simulation setting in SilkPerformer?
You are able to change browser simulations as part of the options. I understand that this changes the http user-agent string that is sent with each http request.
However, what esle does this do and what do the other options do?
For example, does changing browser simulation ever change the thread count used per virtual user (assuming you have the single threaded mode box unchecked)?
Also.. I see that as you switch between browser simulations, the http version box changes. Some browsers allow you to change it while others it is grayed out and set to eather http/1.0 or http/1.1. I was always under the impression that the web server set the http version for you... what am i missing?
any help or just general comments on the subject of browser simulation is appreciated.
[This message has been edited by Corey_G (edited 10-24-2001).]
The browser simulation settings is what defines to SP what a browser is from a traffic perspective. Mostly it is there so that you can create custom browsers if you need to. I would stick with the default settings for the existing browsers though. This way you are sending the traffic the same way that the real browser does.
Performer settings simply match the different browser settings - greyed out items are those that you cannot change in the browser. So, for example, you cannot change HTTP version or threadedness for any Netscape version since they all use HTTP 1.0 and open 4 concurrent threads (max). [Single-thread mode is really for debug only]. Equally you can change HTTP versions for IE versions > 4 since these versions allow you to set HTTP 1.1 or 1.0 usage - not that many people do.
To some degree you can "visualize" the settings differences when you hook the "PerfRun.exe" as a custom application and replay/record a previously recorded script at the same time (if you wish, even record it for the different levels).
That IE uses 4 concurrent connection shows very clearly in the "new" script you get then, for example
Convenience is the first step to enslave yourself. Freedom is inconvenient.
<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by Stronzo: Performer settings simply match the different browser settings - greyed out items are those that you cannot change in the browser. So, for example, you cannot change HTTP version or threadedness for any Netscape version since they all use HTTP 1.0 and open 4 concurrent threads (max). [Single-thread mode is really for debug only]. Equally you can change HTTP versions for IE versions > 4 since these versions allow you to set HTTP 1.1 or 1.0 usage - not that many people do.<HR></BLOCKQUOTE>
OK.. this is getting at the info I am looking for. So you are saying Netscape only uses HTTP 1.0 and uses 4 concurrent threads... How do you know this? This what I want is like specs and stuff for different browsers. Any ideas where to look?
I can tell you the following are the maximum threads each browser will open:
AOL: 2 threads
Netscape: 4 threads
IE3: 8 threads
IE (all other versions): 4 threads
Opera (an excellent European browser): 8 threads
I don't know how I know but I know. You could probably confirm this by reading a technical spedcification of the browsers, if MS & NS make these available.
Easier, is to view the thread count in Task Manager when you open up a browser. Since the numbers above are maximums, it's best to open a very image heavy page where the max threads are likely to be used. There is undoubtedly an Win API call you could use too, but I don't know which it is...
If you had far too much time on your hands you could also probably identify this by reading a Performer record log for each of the browsers. In them you see
etc. The #204 refers to the thread number and by careful reading you may be able to identify the most open at a given time. [Not recommended for the sane].