[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

high performance open source DHCP solution?



If you're just fighting IOPS, another compromise might be using a ramdisk,
and then committing that data to storage every x seconds.

Yes, you might be breaking the RFC, but depending on what it's used for, you
could probably commit every 3-5 seconds without much penalty and limit your
data loss potential on server failure.

Or as others have said... some sort of SSD/cache solution.

On Thu, Jul 21, 2011 at 12:41 AM, Eugen Leitl <eugen at leitl.org> wrote:

> On Wed, Jul 20, 2011 at 05:17:55PM -0700, George Herbert wrote:
>
> > Micron has some large-cap SLC drives in the chain for
> > September/October/ish timeframes.
> >
> > Ramdisk with rsync or rdiffbackup to spinning storage will do just fine.
>
> Or hybrid zfs pools.
>
> --
> Eugen* Leitl <a href="http://leitl.org";>leitl</a> http://leitl.org
> ______________________________________________________________
> ICBM: 48.07100, 11.36820 http://www.ativel.com http://postbiota.org
> 8B29F6BE: 099D 78BA 2FD3 B014 B08A  7779 75B0 2443 8B29 F6BE
>
> _____
> NANOG mailing list
> NANOG at nanog.org
> https://mailman.nanog.org/mailman/listinfo/nanog
>