Send kea-dev mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/kea-dev
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of kea-dev digest..."
Today's Topics:
1. Feature suggestion: LFC time offset (Chaigneau, Nicolas)
----------------------------------------------------------------------
Message: 1
Date: Wed, 6 May 2015 12:48:12 +0000
From: "Chaigneau, Nicolas" <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [kea-dev] Feature suggestion: LFC time offset
Message-ID:
<ab94b0b675bdf14189cd5a861db36c841952e...@de-cm-mbx26.corp.capgemini.com>
Content-Type: text/plain; charset="us-ascii"
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.
------------------------------
_______________________________________________
kea-dev mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/kea-dev
End of kea-dev Digest, Vol 14, Issue 2
**************************************
