In message <CAGfjSCO6PKrumoCS56p9Vs554Pc4=yjsy-en0oyned-j3zq...@mail.gmail.com> , Risto Vaarandi writes: >2014-05-23 10:44 GMT+03:00 Natalia Iglesias > <nigles...@lookwisesolutions.com>>: >> Once we obtain the dump, next critical step is analyzing it. Any clues as >> to what we are looking for? Is there any documentation about dump >> analysis? > >The dump file is in text format and it is designed to be human readable and >self-explanatory. It is divided into a number of sections, [...] > >Since your concern is related to memory consumption, I would recommend to >have a look into the following sections: > >"Pending events" -- the queue of synthetic events. Iif the rules have >generated a very large number of synthetic events, these can consume a lot >of memory. In the end of the section you will see the line "Total: N >elements" which tells you the size of the queue. > >"List of event correlation operations" -- the list of running event >correlation operations (in the end of the section you have the "Total: " >line with the total number) > >"List of contexts" -- the list of created contexts (in the end of the >section you have the "Total: " line with the total number) > >If for each of those lists contains a large number of elements (say, many >millions), it is the likely cause of memory issues. > >There are also three other sections "Pattern match cache", "Child >processes" and "Action list variables", but since items in these lists can >not be generated with variables in their names, it is hard to write a >configuration for these lists becoming excessively large.
I also have used the info from: http://perldoc.perl.org/perldebguts.html#Debugging-Perl-Memory-Usage (PERL_DEBUG_MSTATS, mstat()) in the past to try to find memory leaks. However, since you are running on windows, I am not sure how much that will apply to you. It's quite possible that Strawberry Perl is leaking memory as objects (contexts most likely, but the others are also candidates) are created and destroyed. If your memory use is in contexts, and you manipulate a lot of them, you will also see Perl consuming more cpu as it runs. Since it has to traverse larger and larger associative arrays. Make sure you remove contexts once you are done with them or set short timeouts on the lifetimes of the contexts. -- -- rouilj John Rouillard =========================================================================== My employers don't acknowledge my existence much less my opinions. ------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs _______________________________________________ Simple-evcorr-users mailing list Simple-evcorr-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/simple-evcorr-users
