Question about performance

Wouter Wijngaards wouter at
Tue Jun 13 08:05:55 UTC 2006

Hash: SHA1

Hi Irenäus,

The load is very low? zonec will basically read through the nsd.zones
file and read each of the zone files in turn, read it into memory.
When it is completely done it will write the nsd.database file.
Since the load is low it must be waiting on something. It could be
waiting for the disk - to access the zone files. Zonec does nothing else.
You could try and see how long it takes to access the files - in the
order they are listed in nsd.zones, and cat them to dev null. That
should give the same random access pattern.

If load includes processes waiting for the disk (disk IO), then it must
be waiting on something else, perhaps it is swapping to disk (it reads
the entire database into memory first, 15-30Mb I guess). But you have a
gig of memory, so I guess not.

To accelerate the build process, reordering the names in could
possibly help. Zonec can also build your database by invoking
cat allzonefiles/* | zonec -f nsd.database -o -
(zonefiles need $ORIGIN statements), for zonec this makes little
difference in operation, but the disk access is done by cat.

Best regards,

Irenäus Becker wrote:
> Hello,
> we use nsd version 2.3.3 with currently 53000 active zones. Within nsd.zones - file we have 9000 commented zones, so that our nsd.zones keeps 62000 entrys. The size is 3,5 Mb. All active zones together have 400000 records.
> The application "zonec" needs 5-6 minutes to rebuild nsd.database (current size: 15Mb) on a Sun Fire 280 Ultrasparc III 900MHz with 1GB Ram. 
> The load of Maschine keeps 0.1-0.2 while zonec rebuilds nsd.database.
> My questions are:
> - Do you also need this time to rebuild nsd.database?
> - Why keeps the load at such low level?
> - Is it possible to accelerate the rebuild process?
> Thank you very much,
> Irenäus Becker

Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Fedora -


More information about the nsd-users mailing list