Here are a few recommendations: - Filter events at the receiver - LogFilePatternReceiver provides a 'filterExpression' parameter. Only events that match the expression are processed in the UI.
- Modify VM args - get the bundle from the Chainsaw page and run Chainsaw from the command line, adjusting appropriate parameters (heap, gc, etc) - Make sure the cyclic buffer size is larger than your log file size (using wc -l or another utility) - Cut the file into pieces and load the pieces one at a time Scott -----Original Message----- From: Andreas Knecht [mailto:[EMAIL PROTECTED] Sent: Mon 5/16/2005 5:17 PM To: Log4J Users List Cc: Subject: Large log files chainsaw Hi everyone, I would like to use chainsaw with some production logs (with the filepattern receiver). Only problem is that these logs tend to be around 200-300 MB in size (around 1.2-1.8 Million lines). I've tried increasing the cyclic buffer size to 500000 and chainsaw became more or less unusable as soon as I started the receiver to parse the log file. Has anyone here tried to use chainsaw for similar purposes? Any recommendations? Are there other gui tools to view logs that perform better than chainsaw for this task? Regards, Andreas -- Andreas Knecht Object Consulting Level 25, Northpoint, 100 Miller St North Sydney. NSW 2060 Direct: +61 2 9459 3398 http://www.objectconsulting.com.au/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
