CPU Usage

Gushi google at gushi.org
Tue Jun 26 16:10:09 UTC 2007


On Jun 22, 9:12 pm, Mark Andrews <Mark_Andr... at isc.org> wrote:
> > I'm finding this in my logs:
>
> > clients-per-query increased to 26
>
>         BIND 9.4 will limit the number of simultanious clients it
>         will accept for a given <qname,type,class>.  This ranges
>         between 10 (clients-per-query) and 100 (max-clients-per-query).
>         If named had to drop a client for that tuple and it later
>         go a successful response for that the tuple and the limit
>         hasn't already been raised it will raises the limit by 5.
>         It will then decay over time.
>
>         This message is logged when it does so.
>
>         If you continually get these you may want to adjust
>         clients-per-query to reflect the logged value.
>
>         Mark
> --
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742                 INTERNET: Mark_Andr... at isc.org

Okay, how does that explain this:

last pid: 69123;  load averages:  1.01,  1.02,
1.00                                                        up
5+09:51:10  12:13:15
29 processes:  2 running, 27 sleeping
CPU states: 87.2% user,  0.0% nice, 10.1% system,  2.7% interrupt,
0.0% idle
Mem: 522M Active, 219M Inact, 109M Wired, 112M Buf, 1152M Free
Swap: 967M Total, 967M Free

  PID USERNAME PRI NICE   SIZE    RES STATE    TIME   WCPU    CPU
COMMAND
18208 bind      96    0   516M   516M select  69.6H 93.36% 93.36%
named
  288 root      96    0  1324K   892K select   0:49  0.00%  0.00%
syslogd
  395 root      96    0  7200K  6556K select   0:10  0.00%  0.00%
perl5.8.6
  430 root      96    0  3476K  2876K select   0:09  0.00%  0.00%
sendmail
  461      /     4    0  2504K  1952K accept   0:03  0.00%  0.00%
nrpe2
  450 root       8    0  1364K  1052K nanslp   0:01  0.00%  0.00% cron
  383 root      96    0  1244K   768K select   0:01  0.00%  0.00% usbd
17724 danm      96    0  6116K  2904K select   0:01  0.00%  0.00% sshd
  424 root      96    0  3384K  2488K select   0:00  0.00%  0.00% sshd
  434 smmsp     20    0  3356K  2696K pause    0:00  0.00%  0.00%
sendmail
17728 root      20    0  2548K  1896K pause    0:00  0.00%  0.00% csh
17721 root       4    0  6140K  2844K sbwait   0:00  0.00%  0.00% sshd
69123 root      96    0  2352K  1620K RUN      0:00  0.00%  0.00% top
17727 danm       8    0  1608K  1296K wait     0:00  0.00%  0.00% su
17725 danm       8    0  1708K  1228K wait     0:00  0.00%  0.00% sh
  488 root       5    0  1288K   952K ttyin    0:00  0.00%  0.00%
getty
  490 root       5    0  1288K   952K ttyin    0:00  0.00%  0.00%
getty
  487 root       5    0  1288K   952K ttyin    0:00  0.00%  0.00%
getty
  491 root       5    0  1288K   952K ttyin    0:00  0.00%  0.00%
getty
  492 root       5    0  1288K   952K ttyin    0:00  0.00%  0.00%
getty
  489 root       5    0  1288K   952K ttyin    0:00  0.00%  0.00%
getty
  494 root       5    0  1288K   952K ttyin    0:00  0.00%  0.00%
getty
  493 root       5    0  1288K   952K ttyin    0:00  0.00%  0.00%
getty
  209 root      20    0  1192K   648K pause    0:00  0.00%  0.00%
adjkerntz
  266 root     114    0   516K   356K select   0:00  0.00%  0.00% devd

What could possibly be going on here, and how can I fix it?

-Dan



More information about the bind-users mailing list