[Subject Prev][Subject Next][Thread Prev][Thread Next][Subject Index][Thread Index]
Re: Linux Kernel scheduling
- To: linux-india-programmers@xxxxxxxxxxxxxxxxxxxxx
- Subject: Re: Linux Kernel scheduling
- From: Arun Sharma <arun@xxxxxxxxxxxxxxx>
- Date: Sun, 1 Apr 2001 19:28:41 -0700
- In-reply-to: <002201c0b900$89338f10$8900000a@aclindia.com>; from ambarroy@iname.com on Fri, Mar 30, 2001 at 03:32:30PM +0530
- References: <021f01c0b6b5$358ca740$8900000a@aclindia.com> <20010327215735.A24174@sharmas.dhs.org> <00bf01c0b839$f3f68540$8900000a@aclindia.com> <20010329083345.A28434@sharmas.dhs.org> <002201c0b900$89338f10$8900000a@aclindia.com>
- User-agent: Mutt/1.2.5i
On Fri, Mar 30, 2001 at 03:32:30PM +0530, Ambar Roy wrote:
> > Not necessarily. You could use thread pooling to get fewer threads to
> serve
> > that many connections. All the appservers in the market do this.
> Even with thread pooling, i can still maintain only 1 open connection per
> thread at a time. Basically here we are making a server, which needs to
> maintain an open connection with each connected client.
If the average time a connection is open is relatively small, you
should still be ok. I'd start with a small number of threads and
increase them only when the server becomes unresponsive by running
out of threads.
-Arun