DHCPD performance -- solid-state disks?
ray at selu.edu
Fri Sep 9 15:20:42 UTC 2011
As others may chime in, I believe your best bet is to create a ramdisk and
store the leases file there. That's your best performance. Also note your
logging, as our /var/log/messages file (on CentOS) also gets hit pretty
Your start/stop scripts should copy the lease file to/from the ramdisk. And
you should probably have a script to copy the lease file to disk every few
minutes as well.
Southeastern Louisiana University
email: ray at selu.edu
On Fri, Sep 9, 2011 at 9:51 AM, John Hascall <john at iastate.edu> wrote:
> We are starting to see our dhcpd server unable to cope with
> our peak load (the top of the hour when students move from
> one building to another). Ideally, our wireless infrastructure
> would allow them to keep their address as they roam, but this
> is not the case, so we see large surges in lease-swapping during
> these 10 minute periods. It looks like we can do about 50/second
> with our current hardware. The CPUs are never above a few percent
> busy, so my belief is that we are limited by our synchronous-write
> speed to the lease file. Does this seem correct?
> We are currently using mirrored 15k SAS drives. Is our best
> move to go to solid-state disk?
> Thanks for any advice you might have!
> dhcp-users mailing list
> dhcp-users at lists.isc.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the dhcp-users