named.memstats file question

[Mark_Andrews at isc.org]

> 
> Greetings,
> 
> I have a question on named.memstats output from BIND version 8.3.1.
> 
> Maybe it's me, but I just can't seem to lay hands on a good source of
> documentation for the named.memstats file, with an emphasis on how to
> parse it to get a feeling for how well one's nameserver is performing,
> if in fact such information can be gleaned from this file.  Lines
> such as the following:
> 
>     142:           2 gets,           0 rem
>     144:         746 gets,           1 rem (1 bl, 27 ff)
>     168:         943 gets,           1 rem (1 bl, 23 ff)
>     169:           2 gets,           0 rem
>     192:         552 gets,           1 rem (1 bl, 20 ff)
>     196:           2 gets,           1 rem (1 bl, 19 ff)
>     216:         939 gets,           0 rem (1 bl, 18 ff)
>     240:        1558 gets,           0 rem (1 bl, 17 ff)
>     256:           3 gets,           3 rem (1 bl, 13 ff)
>     264:         811 gets,           0 rem (1 bl, 15 ff)
>     288:         162 gets,           0 rem (1 bl, 14 ff)
>     312:         120 gets,           0 rem (1 bl, 13 ff)
>     336:         227 gets,           0 rem (1 bl, 12 ff)
>     360:         189 gets,           0 rem (1 bl, 11 ff)
>     384:          58 gets,           0 rem (1 bl, 10 ff)
>     388:           6 gets,           0 rem (1 bl, 10 ff)
>     408:          26 gets,           0 rem (1 bl, 10 ff)
>     432:          58 gets,           0 rem (1 bl, 9 ff)
>     456:          67 gets,           0 rem (1 bl, 8 ff)
>     460:           9 gets,           9 rem (2 bl, 7 ff)
>     480:          72 gets,           0 rem (1 bl, 8 ff)
>     499:           5 gets,           0 rem
> 
> sure do look interesting as all get out, but I can't find anything
> anywhere to tell me how to read them.  The 4th edition of DNS and BIND
> makes reference to some neat tools at
> 
>     http://www.dns.net/dnsrd/tools.html
> 
> but, sadly, that site appears to be not accepting connections this
> afternoon from my location.  :-(
> 
> Anyone got any pointers on how I might make use of these stats?
> 
> Thanks.
> 
> -- 
> Todd Herr                                         todd at angrysunguy.com
> 
> 
> 
	memstats along with MEMCLUSTER_RECORD=1 and deallocate-on-exit
	is used to track memory leaks.  Note, if the parser detects a
	error there will be memory leaks due to the nature of the
	recovery machanisms.

	memstats was orignally used to detemine if we were using the
	right constants in the memory all system.

	Mark
--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at isc.org