[kea-dev] Suggestions for DHCP packets logs

[Angelo Failla]

From: Chaigneau, Nicolas <nicolas.chaigneau at capgemini.com><mailto:nicolas.chaigneau at capgemini.com>
Date: June 12, 2015 at 10:11:42 AM
To: Kea Dev List <kea-dev at lists.isc.org>><mailto:kea-dev at lists.isc.org>
Subject:  [kea-dev] Suggestions for DHCP packets logs

1) don't use log4cplus

There is a very significant performance penalty when logging a large volume of data through log4cplus.

Packets should not be logged through log4cplus.
Packets should be written directly through a fstream. (I've measured about 30% improvement in DORA/s capacity, as compared to using log4cplus).

can’t you use Google’s GLOG framework? it supports log rotation and other things. it’s what C++ backend services at Facebook are using.

We don’t use the log rotation facility in GLOG, we just let applications write to stderr/stdout and we use `runit` (http://smarden.org/runit/), which handles application supervision and log file rotation via the `svlogd` daemon (http://smarden.org/runit/svlogd.8.html). that’s how we also deployed KEA internally.

-Angelo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/kea-dev/attachments/20150612/aa96280d/attachment.html>