Re: [squid-users] relation between http req/sec and no of simulatneous accesses

From: khiz code <khizcode@dont-contact.us>
Date: Fri, 12 Oct 2001 03:42:38 -0700 (PDT)

Hi alex
Iam sorry but i dont quite understand "benchmark peak" and "squid peak"
so for a mean response time of 0.5 secs total no of concurrent
connections shall be 70*0.5 =35 ??? so less

TIA
khiz
--- Alex Rousskov <rousskov@measurement-factory.com> wrote:
> On Thu, 11 Oct 2001, khiz code wrote:
>
> > my cache could go upto abt 70 req/sec
> > what i would like to understand is that 70 req/sec corresponds to
> abt
> > how many simultaneous client connections ..i.e how many clients can
> the
> > cache serve at any point of time
> >
> > Robin stevens had given a figure of 2500 simultaneuos access for
> > 150 req/sec so cud i apply simple math logic to arrive at a
> > corresponding statistic for 70 req/sec which turns out to be
> > roughly 1000 simultaneous accessess ???
>
> You cannot apply "simple math logic" here unless your response times
> are the same as what Robin Stevens observed.
>
> I think there is only one formula that ties the number of
> active concurrent connections (C) and request rate (R):
> C = R * mean_request_response_time
> The above does not account for idle persistent connections, of
> course.
> C has little to do with the number of users. One user can have 1, 3,
> 4, or any number of connections open, depending on what kind of a
> "user" they are.
>
> N.B. Make sure your 70/sec peak is not a benchmark bottleneck (as
> opposed to Squid peak).
>
> Alex.
>
>

__________________________________________________
Do You Yahoo!?
Make a great connection at Yahoo! Personals.
http://personals.yahoo.com
Received on Fri Oct 12 2001 - 04:42:40 MDT

This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:02:41 MST