[Bro-Dev] manager-child cpu utilization?

Martin Holste mcholste at gmail.com
Sat Sep 17 19:17:38 PDT 2011

Yep, this is definitely happening.  Our cluster's manager and its
child, as well as the proxy and its child chew up about 20-25% CPU
each, so that's almost a full CPU for the manager/child and

On Fri, Sep 16, 2011 at 7:52 PM, Seth Hall <seth at icir.org> wrote:
> I'm seeing what appears to be extremely high CPU utilization by the manager's child process in a rather large (23 worker?) cluster.  I believe the deserialization is being done by the child process and I'm guessing that the child process is being overwhelmed by all of the deserialization it's having to do for the logging framework's log records.
> Any one have thoughts about if I'm correct or ways this could be optimized?  I'm just worried this could become a problem because logs are written much faster at other sites and I can see other sites getting communication framework overload really easily.  I think it's something that we need to keep a close eye on at least.
>  .Seth
> --
> Seth Hall
> International Computer Science Institute
> (Bro) because everyone has a network
> http://www.bro-ids.org/
> _______________________________________________
> bro-dev mailing list
> bro-dev at bro-ids.org
> http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev

More information about the bro-dev mailing list