This discussion focuses primarily on serving static files to a client, not processing dynamic web pages. Most people running tomcat are processing dynamic pages, like getting data from a database and compositing a page based on that data.
An FTP site, or a static web site will typically be I/O bound or Network bound, and the only way to increase throughput it to increase the number of I/Os per second that your server can manage or increase the size of your network interface. A java based dynamic website is typically not I/O bound, but CPU bound, which posses a different set of challenges than a static FTP server. Alex. On 6/21/06, Andrew Miehs <[EMAIL PROTECTED]> wrote:
Now that we are moving to the theoretical discussion, you will probably want to have a look at http://www.kegel.com/c10k.html Regards Andrew On 21/06/2006, at 4:56 PM, Mladen Adamovic wrote: > I spoke recently with guy from Microsoft (project manager from > server division). > He said that heavily loaded web server don't lose much time to > switch processes but when you are out of free memory and server > start to swap, performances degrade dramatically. > I though that guy definitely knew what he was thought about. > > Lets see what operating system has to do when switch threads. > Just to move all registers to/from memory? Anything else? --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]