Re: [Asterisk-java-users] Advanced Event Filtering
Brought to you by:
srt
From: Aaron E. <aar...@gm...> - 2007-08-03 01:06:39
|
As a general rule, I try to keep my swap at 0 always. Swap is very bad, not just for java. :D On 8/2/07, Brett Sutton <bs...@no...> wrote: > I would be very surprised if you have any problems with the garbage > collector. > > We have done a lot of work in this area for a large client running a > very heavily loaded java based web server (tomcat). > The garbage collector is super fast. > > The only problem we ever had was if we let the java app swap memory out > to the page file. > This is super dangerous with java. > [This took us about 6 weeks of heavy diagnosis to discover the root > cause of, hence the experience with the java GC. This is the only bug > that I've every resolved by 'touch'. I happened to put my hand on the > system unit during garbage collection and felt the drive rumbling :)] > > The Tenured area of the garbage collector can grow quite big and remain > untouch for lengthy periods of time. > The OS will then page this area out to disk. When a tenured garbage > collection occurs the tenured area has to be pulled from disk. This can > turn a GC which normally takes 300 milliseconds into a 2 minute process. > > Regards, > Brett. > > > > Stefan Reuter wrote: > > Hi, > > > > my first thought when reading this thread was: If it's not broken, don't > > try to fix it. It seems you did not experience any problems with garbage > > collection (though you might run some load tests to verify that in your > > environment). Java is really smart handling small short-lived objects. > > The garbage collector has a young generation (eden space) designed for > > just that purpose. > > > > The next thing that comes to my mind is what you might actually achieve > > by filtering events at the java side. You will still have create some > > strings and build the map representing the events (note that the > > management api makes no guarantees regarding the order of the attributes > > so you have to parse at least until you encounter the "Event: XXX" > > attribute). What you could save is creating the actual event object, but > > well... > > > > I would recommend to really get some numbers using a decent profiler. If > > you can provide something that is convincing we might very well have a > > look at supporting it in future Asterisk-Java releases. > > > > =Stefan > > > > > > ------------------------------------------------------------------------ > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Splunk Inc. > > Still grepping through log files to find problems? Stop. > > Now Search log events and configuration files using AJAX and a browser. > > Download your FREE copy of Splunk now >> http://get.splunk.com/ > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > Asterisk-java-users mailing list > > Ast...@li... > > https://lists.sourceforge.net/lists/listinfo/asterisk-java-users > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Asterisk-java-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/asterisk-java-users > |