> > It's very hard to use processes for this purpose. Consider,
> > for example, a
> > web server. You don't want to use one process for each client
> > because that
> > would limit your scalability (16,000 clients would become difficult, and
> > with threads it's trivial). You don't want to use one thread
> > for each client
> How is it trivial? How do you debug a 16,000 thread application?
As I said, you don't want to use one thread for each client. You use, say,
10 threads for the 16,000 clients. That way, if an occasional client
ambushes a thread (say by reading a file off an NFS server or by using some
infrequently used code that was swapped to a busy disk), your server will
keep on humming.
DS
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/