Re: Scalable tcp server
- From: Rick Jones <rick.jones2@xxxxxx>
- Date: Mon, 9 Jul 2007 18:26:54 +0000 (UTC)
Henrik Goldman <henrik_goldman@xxxxxxxxxxxx> wrote:
In my test I wrote a client application which simulates up to 500
clients by spawning 500 threads. Each thread would then connect to
the server and perform a request. When the server is empty the
request takes about 250 ms. However with 500 idle clients connected
each request takes about 890 ms. This means that each request gets
slowed down by several times.
How do you know some of that isn't in the client? If I were looking
to measure the scalibility of a server I'd want to have several
clients, not just one client process with 500 threads. Or, I'd want
to check the client first by testing it against several servers at
once.
The suggestion to profile things is spot-on.
rick jones
--
web2.0 n, the dot.com reunion tour...
these opinions are mine, all mine; HP might not want them anyway... :)
feel free to post, OR email to rick.jones2 in hp.com but NOT BOTH...
.
- References:
- Scalable tcp server
- From: Henrik Goldman
- Scalable tcp server
- Prev by Date: Re: Problem with syscall(2)
- Next by Date: What errno value should I receive if trying to create a file an a read-only NFS volume
- Previous by thread: Re: Scalable tcp server
- Next by thread: Re: Scalable tcp server
- Index(es):
Relevant Pages
|
