Hi list!
I have been bothered by this for some time now, and never took the time to
ask.
I have shinken running with Thruk/Livestatus, monitoring an environnement of
a respectable size (3000 servers with 16000 services). Thanks to Jean, who
had the patience to do a lot of fixing for us, it now runs fine.
I'm having performance issues with Thruk though, and it might be connected
to my other concern, which is the livestatus.db size. For example, I can
display the unhandled hosts problems page in less than 5 seconds but
unhandled services problems page can take up to 15 seconds to be sent to my
browser.
-rw-r--r-- 1 shinken shinken 132171776 May 18 16:22 livestatus.db
It's not really the size itself that bothers me, but rather the fact that
it's growing. In less than 2 month, I've seen it slowly growing from 40-60
MB to 130MB today.
So my questions are :
- Is this size normal?
- How can I estimate the size of livestatus.db if it stabilises?
- Can the DB size be responsible for my performance problems in Thruk, or
should I accuse Shinken Livestatus broker?
Denis
PS: I managed to get slightly better results using fast_cgi, but only for
the HTML generation part, not the query part in the broker, especially when
many users connect to the UI
------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its
next-generation tools to help Windows* and Linux* C/C++ and Fortran
developers boost performance applications - including clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Shinken-devel mailing list
Shinken-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shinken-devel
