stacksize tuning SunOS 5.8

vincent.blondel at ing.be vincent.blondel at ing.be
Wed Sep 17 07:38:39 UTC 2008


 

> Hello all,
>
> I get some SunOS 5.8 boxes running BIND 9.4.1-P1 compiled from my own.
These dns nameservers run very well  and answer to some 1500 req/sec
without any > interface error, kernel panic, reboot or something else.
(for info the uptime is between 400 and 600 days).
>
> Now I look for some BIND internal values including memory, stack
memory usage, .... so I know if I have to tune some named.conf
parameters or not ?
>
> Is there somebody reading this list getting some experience in this
domain and eventually help me in this task ??
>

I just experienced some commands. Let me explain my little labo ..

# ./queryperf -d queriesperf.txt -l 60

DNS Query Performance Testing Tool
Version: $Id: queryperf.c,v 1.8.192.4 2007/09/05 07:44:57 marka Exp $

[Status] Processing input data
[Status] Sending queries (beginning with 127.0.0.1)
[Timeout] Query timed out: msg id 9
[Timeout] Query timed out: msg id 15
[Timeout] Query timed out: msg id 16
[Timeout] Query timed out: msg id 17
[Timeout] Query timed out: msg id 18
[Timeout] Query timed out: msg id 19
[Timeout] Query timed out: msg id 20
[Status] Testing complete

Statistics:

  Parse input file:     multiple times
  Run time limit:       60 seconds
  Ran through file:     315344 times

  Queries sent:         315345 queries
  Queries completed:    315338 queries
  Queries lost:         7 queries
  Queries delayed(?):   0 queries

  RTT max:              0.041352 sec
  RTT min:              0.000115 sec
  RTT average:          0.003633 sec
  RTT std deviation:    0.000941 sec
  RTT out of range:     0 queries

  Percentage completed: 100.00%
  Percentage lost:        0.00%

  Started at:           Wed Sep 17 09:24:16 2008
  Finished at:          Wed Sep 17 09:25:16 2008
  Ran for:              60.004846 seconds

  Queries per second:   5255.208888 qps

# pmap -x 8415
8415:       /usr/local/sbin/named -u named -t /opt/named
 Address   Kbytes Resident Shared Private Permissions       Mapped File
00010000    2096    2096    2096       - read/exec         named
0022A000      72      72      24      48 read/write/exec   named
0023C000   18720   18720       -   18720 read/write/exec     [ heap ]
FDDE0000       8       8       8       - read/write/exec/shared   [ anon
]
FE802000       8       8       -       8 read/write          [ anon ]
FE904000       8       8       -       8 read/write          [ anon ]
FEA06000       8       8       -       8 read/write          [ anon ]
FEB08000       8       8       -       8 read/write          [ anon ]
FEC06000       8       8       -       8 read/write          [ anon ]
FEC0A000       8       8       -       8 read/write          [ anon ]
FED08000       8       8       -       8 read/write          [ anon ]
FED0C000       8       8       -       8 read/write          [ anon ]
FEE0A000       8       8       -       8 read/write          [ anon ]
FEE0E000       8       8       -       8 read/write          [ anon ]
FEF0C000       8       8       -       8 read/write          [ anon ]
FEF10000       8       8       -       8 read/write          [ anon ]
FF00E000       8       8       -       8 read/write          [ anon ]
FF090000       8       8       -       8 read/write          [ anon ]
FF0B0000       8       8       -       8 read/write          [ anon ]
FF0CA000      32      32       -      32 read/write          [ anon ]
FF0EC000      24      24       -      24 read/write          [ anon ]
FF100000     688     688     688       - read/exec         libc.so.1
FF1BC000      32      32       8      24 read/write/exec   libc.so.1
FF1D0000       8       8       -       8 read/write/exec     [ anon ]
FF1E0000      24      24      24       - read/exec
nss_files.so.1
FF1F6000       8       8       8       - read/write/exec
nss_files.so.1
FF214000       8       8       -       8 read/write          [ anon ]
FF220000      16      16      16       - read/exec         libmp.so.2
FF234000       8       8       8       - read/write/exec   libmp.so.2
FF240000     112     112     112       - read/exec
libthread.so.1
FF26C000       8       8       -       8 read/write/exec
libthread.so.1
FF26E000      48      48       -      48 read/write/exec
libthread.so.1
FF280000     576     576     576       - read/exec         libnsl.so.1
FF310000      40      40      24      16 read/write/exec   libnsl.so.1
FF31A000      24      16      16       - read/write/exec   libnsl.so.1
FF330000       8       8       8       - read/write/exec/shared   [ anon
]
FF340000       8       8       -       8 read/write/exec     [ anon ]
FF350000      24      24      24       - read/exec
libpthread.so.1
FF366000       8       8       8       - read/write/exec
libpthread.so.1
FF370000      40      40      40       - read/exec
libsocket.so.1
FF38A000       8       8       -       8 read/write/exec
libsocket.so.1
FF390000       8       8       -       8 read/write/exec   libdl.so.1
FF3A0000       8       8       8       - read/exec         libc_psr.so.1
FF3B0000     192     192     192       - read/exec         ld.so.1
FF3E0000       8       8       -       8 read/write/exec   ld.so.1
FF3E2000       8       8       -       8 read/write/exec   ld.so.1
FFBEA000      24      24       -      24 read/write          [ stack ]
--------  ------  ------  ------  ------
total Kb   23016   23008    3888   19120

As far as I can see, the perf test reached some 5255 requests a second
and the process consumes some 23 Mb. 

I ran pmap command continuously while the test and the memory usage did
not increase so ... is that normal, do I have to run another command to
monitor the stack memory usage of one process ????

I hope this can be used as the basic point for a little discussion ..

Many thks for your help ..

> Many thks
> Vincent.

-----------------------------------------------------------------
ATTENTION:
The information in this electronic mail message is private and
confidential, and only intended for the addressee. Should you
receive this message by mistake, you are hereby notified that
any disclosure, reproduction, distribution or use of this
message is strictly prohibited. Please inform the sender by
reply transmission and delete the message without copying or
opening it.

Messages and attachments are scanned for all viruses known.
If this message contains password-protected attachments, the
files have NOT been scanned for viruses by the ING mail domain.
Always scan attachments before opening them.
-----------------------------------------------------------------




More information about the bind-users mailing list