home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.mail.uucp:2443 comp.mail.sendmail:3073 comp.unix.sys5.r4:1026 comp.unix.questions:14994
- Newsgroups: comp.mail.uucp,comp.mail.sendmail,comp.unix.sys5.r4,comp.unix.questions
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!hobbes.physics.uiowa.edu!news.iastate.edu!john
- From: john@iastate.edu (John Hascall)
- Subject: Re: DNS name servers
- Message-ID: <Bzz5rF.Huq@news.iastate.edu>
- Sender: news@news.iastate.edu (USENET News System)
- Organization: Iowa State University, Ames, IA
- References: <Bzx9r5.FDo@gator.use.com> <BzyMur.C6s@solaria.mil.wi.us>
- Date: Mon, 28 Dec 1992 15:02:03 GMT
- Lines: 23
-
- jgreco@solaria.mil.wi.us (Joe Greco) writes:
- ...
- }Since you're using a nameserver with a cache, it saves all requests that it
- }has had to resolve to the cache. Resolving a name is an "expensive"
- }operation, often involving several other servers. The savings in time
- }offered by the cache is great compared to the relatively tiny overhead of
- }RAM and time to cache it.
-
- True enough, however, it is possible to eat up mucho RAM. For example:
-
- USER PID %CPU %MEM SZ RSS TT STAT TIME COMMAND
- root 7882 0.0 30.3 13320 4384 ? S 0:09 /etc/named
- \________/
- in KBytes
-
- (because we are a large site and have Hesiod we have lots of nameserver data)
-
- John
- --
- John Hascall ``An ill-chosen word is the fool's messenger.''
- Systems Software Engineer
- Project Vincent
- Iowa State University Computation Center + Ames, IA 50011 + 515/294-9551
-