I have added a Cache manager to my test which is cleared on each iteration and checked the option of retrieving all embedded resources from HTML files. I'm also using concurrent pool with a size of 8. Doesn't that give higher or closer times to those seen by end user?
Regards Sam On Mon, Jul 1, 2013 at 3:44 PM, Deepak Shetty <[email protected]> wrote: > Ill also add that the times are usually as seen by the end user - so the > times as seen by Jmeter usually have to be lesser (since these are max > times you need to consider empty cache for first time access or slower > networks etc). You also usually use something like 90 or 95 percentile > > > On Mon, Jul 1, 2013 at 12:42 PM, Deepak Shetty <[email protected]> wrote: > > > >Does that mean I should not go beyond 50 or should I still do tests with > > a higher number? > > You usually have to factor in growth (growing at a rate of X users per > > month or whatever with whenever is your next scheduled release where you > > could make reasonable amount of optimisations) - i.e. capacity planning. > > > > > > >How can I go about establishing baselines for page load times, if I do > > not have any historic data and have no industry benchmarks or >competitor > > data. > > There are some usability tests as to what times cause user's to perceive > > as slow. (Normal navigation has different values then login or search or > > more secure pages like checkout) - you can google these. These are > specific > > to industry and functionality. (for e.g. we have 2 seconds for search > page > > (most heavily used part of the website) , 4 seconds for catalog pages, > > 6seconds for login/secure pages/ pages that have any ERP integration) - > but > > its better if you actually conduct some usability tests with end usersor > if > > you can find equivalents for your industry. > > > > > > >Would it make sense to say let's see how the website is doing throughout > > >the development phase and establish our baseline using the current > > response > > >times? > > No! you have to determine the times you want(as above) and see that your > > current response satisfies those (suppose your current page takes 60 > > seconds are you satisfied that , that is your baseline?) > > > > > > On Mon, Jul 1, 2013 at 12:33 PM, nmq <[email protected]> wrote: > > > >> Hi all > >> > >> This is not a JMeter specific questions but since this user list > comprises > >> of experts in performance testing, I figured it would be a good place to > >> ask this question. > >> > >> My question is how do you establish baselines for a website's > performance > >> if you do not have any historic data? Lets say this is a new website > and > >> its for a limited number of customers. > >> > >> How do you determine what should be the number of concurrent users you > >> should simulate. > >> > >> Lets say the executives say off at the top of their heads, that the > >> maximum > >> number of concurrent users would be 50 at peak times. Does that mean I > >> should not go beyond 50 or should I still do tests with a higher number? > >> > >> How can I go about establishing baselines for page load times, if I do > not > >> have any historic data and have no industry benchmarks or competitor > data. > >> > >> Would it make sense to say let's see how the website is doing throughout > >> the development phase and establish our baseline using the current > >> response > >> times? > >> > >> I would appreciate any input. > >> > >> > >> Regards > >> Sam > >> > > > > >
