[kea-dev] Feature suggestion: LFC time offset

[Chaigneau, Nicolas]

Hello,



Currently, LFC execution is controlled through a single parameter: "lfc-interval".

I've noticed that when LFC runs, when dealing with large lease files, it will consume 100% of the CPU on which it is running.
In itself, this is not an issue on a multi-CPU architecture (Kea runs on a CPU, LFC on another).

In my setup, though, I have multiple Kea instances running on the same server.
Typically, they will all be started at the same time.
Consequently, all LFC processes will also be running at the same time.

The LFC is very CPU-intensive, but is only running intermittently.

So I'm thinking that it would be a good idea to allow more flexibility on when LFC is executed.
What do you think of adding an "lfc-offset" parameter, which would mean that the first execution of LFC would be at "lfc-offset + lfc-interval" ?

Each Kea instance could be set up with a different "lfc-offset" value.
This would allow to space the execution of the various LFC processes over time, hence optimizing the CPU usage.



Regards,
Nicolas.

This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.