loadrunner An interesting discussion on browsers and...

  • perf-test.com need your contributions to build up a strong repository of performance engineering resources.

J

James Pulley

Guest
An interesting discussion on browsers and number of connections per host that is interesting reading. Of particular note is that HP defaults to 6 (The w3c standard for browsers), but if your recording browser uses fewer, such as IE, then the number of concurrent connections is set to a lower level. This is particularly important if you modify one script to represent multiple browser types by changing the user agent. In tandem with changing the user agent then you also potentially need to change the number of maximum connections per host based upon the browser type. Watching what browser manufacturers do on the connections front is an interesting watch. Some prefer to minimize the number of hard connections to the server and leverage pipelining to maximize efficiency on a single connection without the overhead of establishing an additional hard connection where others take the hit on the hard connection seeking parallelism as the performance path If you are not a subscriber to Stackoverflow then you are missing out on gems like this one. 'Pulley
safe_image.php
 
Sort by date Sort by votes
Yes, it's especially important today for getting the playback options correct represented. We were stuck for the most part with IE and 2 connections with html 1.1 for years. Now we hard set those in the scripts to be 6 or 8 even 16 depending on what we need to simulate. Good read!
 
Upvote 0 Downvote
Interesting. I was just doing some teaching today and user agent came up. I couldn't think of a good example for changing it. Now I have a great reference to use. Thanks Pulley!
 
Upvote 0 Downvote
Some dynamic html solutions include conditional page generation by browser type. Oddly enough the "php for dummies" books represent this challenge well on handling the non standard oddities of certain browsers
 
Upvote 0 Downvote
That is a fine example. I can safely say I've not seen an app handle browsers differently in any meaningful use case except for, perhaps, "We don't support (IE/Mozilla/Chrome/Safari)." But that would be such an edge case that I can see scripting it.
 
Upvote 0 Downvote
Prior to version 8 IE had a not of non standard html oddities for page representation. So you can still find some conditional page generation directives or there for IE pre 8. It can really hose you on correlation if you change the user agent string and the page structure changes around your captured variable. Something to keep an eye out for
 
Upvote 0 Downvote
And don't forget the dynamic page generation/changes that some newer technologies also employ based on geolocation too! That was a fun one to script for and validate.
 
Upvote 0 Downvote
You must log in or register to reply here.
Top Bottom
Back