[Kea-users] Sizing Guide

[Darren Ankney]

Hi Joseph,

It is not an easy question to answer.  It always depends on the
particular deployment and client behavior.  If you aren't tight on
resources: over provision.  Kea can be tuned to use a certain number
of CPUs (performance degrades if it uses more than 16).  You can also
tune logging to only take up so much disk space.  Perhaps 500GB of
disk but that is just a wild guess.  RAM, when using a database, is
always: "as much as you can spare".  Probably at least 16GB.  If your
database server has to wait on the disk, it will be slow, so fitting
tables into RAM (disk cache and the database server itself) is
important.  You should be ready to change any of these values,
however, in the case they be too much or not enough.

Thank you,
Darren Ankney

On Mon, Jun 24, 2024 at 10:26 AM Joe Craig <JCraig at applieddigital.com> wrote:
>
> Hello,
>
>
>
> I’m looking for recommendations for sizing Kea nodes is there a guide out there that I can follow for sizing or would someone in the community help me determine the size that I would need?
>
>
>
> Architecture Overview:
>
>
>
> 2 Kea servers with Postgresql locally installed on each of the nodes set up in Failover configuration.
>
> Support needed for 30k DHCP leases.
>
> Close to 100 DHCP scopes in our configuration.
>
> Running on VMWare.
>
>
>
> I have flexibility with node count and with sizing of the VMs.
>
>
>
> Thanks,
>
>
>
> Joseph Craig
> Systems Engineer
>
>
>
> --
> ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information.
>
> To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users.
>
> Kea-users mailing list
> Kea-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/kea-users