We were seeing similar issues with low leases, moved the dhcpd.leases file to a ramdisk and went from ~200 leases per second to something like 8,000 leases per second.
On Tue, Jul 19, 2011 at 11:08 PM, George Herbert <george.herb...@gmail.com>wrote: > 220-ish per second sounds roughly like a 1-disk (or 2 mirrored disk) > IOPS problem, personally... > > But any number of other things could be affecting it. > > The number should be thousands if your disk / filesytem RAM cache / > server configuration aren't inadequate... > > On Tue, Jul 19, 2011 at 8:54 PM, Jimmy Hess <mysi...@gmail.com> wrote: > > On Tue, Jul 19, 2011 at 9:21 PM, Rogelio <scubac...@gmail.com> wrote: > >> The free DHCP solution, ISC, seems to be having scaling issues (i.e. > >> handling only about 200 DHCPDISCOVER and 20 DHCPRENEW requests), and I > >> was wondering if anyone had any open source suggestions of solutions > >> that could scale much better? > > > > Where do you get that ISC DHCPD only handles 200 DHCPDISCOVER / 20 > DHCPRENEW > > requests? That doesn't sound right. So I wonder what are you > measuring? > > > > Is this a number of answers per second your implementation of ISC > > DHCPD is providing successfully? > > There are architectural facts about any environment besides what > > software is performing the DHCP task. > > > > How many I/Os + fsync()'s per second can this DHCP server handle > > that does only 20 renews? > > > > -- > > -JH > > > > _____ > > NANOG mailing list > > NANOG@nanog.org > > https://mailman.nanog.org/mailman/listinfo/nanog > > > > > > -- > -george william herbert > george.herb...@gmail.com > > _____ > NANOG mailing list > NANOG@nanog.org > https://mailman.nanog.org/mailman/listinfo/nanog > _____ NANOG mailing list NANOG@nanog.org https://mailman.nanog.org/mailman/listinfo/nanog
