hi, i've been thinking about https://dev.icinga.org/issues/1259 quite a bit today, and i wanted to try a new approach - not buffer ido2db, but buffer idomod between core and socket.
the outcome can be reviewed on git, and i do think that with this commits, this really works. at least my system now takes 2 seconds to start with loaded idomod. basic idea is to change the output_buffer to a mutex locked circular buffer, and start a queue thread after daemonizing. the main core process writes only the buffer, and then returns. the queue thread reaps the buffer and then writes to data sink. even the config dump is moved into the event loop, so the overall delay is reduced once more. the default is 50k items, my system takes ~2k to 5k items with 200 hosts and 4k services. cost is cpu time - and a bit memory. and i need a lot of different systems for testing!!! https://git.icinga.org/?p=icinga-core.git;a=commit;h=a34a89917b28f537af17cd5d7c13d9ab924299a6 https://git.icinga.org/?p=icinga-core.git;a=shortlog;h=refs/heads/test/ido thx michi -- DI (FH) Michael Friedrich Vienna University Computer Center Universitaetsstrasse 7 A-1010 Vienna, Austria email: michael.friedr...@univie.ac.at phone: +43 1 4277 14359 mobile: +43 664 60277 14359 fax: +43 1 4277 14338 web: http://www.univie.ac.at/zid http://www.aco.net Icinga Core& IDOUtils Developer http://www.icinga.org ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2 _______________________________________________ icinga-users mailing list icinga-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/icinga-users
