On Wed, May 18, 2011 at 5:48 PM, Gerhard Lausser
<gerhard.laus...@consol.de>wrote:
> Hi,
>
> [...]
>
> The performance problems are another thing. I need to play around, maybe I
> find a better algorithm. Does your monitoring server have enough memory? I
> always see the livestatus broker process eat lots of it. What surely helps,
> is to put the broker on a separate machine.
>
Hi,
Maybe we can find a way to enable a cprofile call for external modules? So
we will profile it in real conditions and see where we got the performance
problem.
I though about some perf tuning tricks, like for some common filter (bad
status) get already available and uptodate set() so we can have all filter
look at only a small part of the hosts/services instead of all of them (or
just get a "default order" so we are sure the first filter will give the
less elements to help other filter to parse even less elements, etc).
But let profile it first before we tune something that is not the
performance problem point :)
Jean
>
>
> Gerhard
>
>
>
>
>
------------------------------------------------------------------------------
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
