Le Fri, Mar 08, 2002, à 01:36:21PM -0600, Chad C. Walstrom a écrit: > On Fri, Mar 08, 2002 at 06:38:00PM +0100, Cyrille Chepelov wrote: > > ...as opposed to at worst one resolution per hit, possibly cached a > > couple minutes by the local DNS or by an extra piece of bloat in the > > web server proper. > > What about nscd? Sure, the webserver still has to do hostname > resolution, but it's cached at the library level. No server bloat > necessary. Sure, nscd eases things a bit. However, while the actual resolution takes place, you still have one thread locked waiting for nscd to finish its task, should the hostname not be in nscd's cache. And, by Murphy's law, it's when you're making a demo of your spiffy new webserver that a cluster of hosts with bad (unresponsive DNSes) connect and tie up a bunch of threads... Not a concern for every installation, but there are many a case where it is... -- Cyrille -- Grumpf.
Attachment:
pgpQqNLs7K8ac.pgp
Description: PGP signature