Very good job. That is quite impressive given the complications of the transport. It looks easier to use.
Daniel Wanja
Tue, 26 Feb 2008 14:30:06 GMT
The very first version of the log visualizer was using not an AIR application, it was a Flex front-end with a Ruby log file parsing and was able to process larger log files (i.e. 4gb in 10minutes), I haven’t tried with such large files since I am now “rollling” the logs and analyze smaller log files. Also I couldn’t get the feedback/progress of the parsing to refresh the display which would give a good indication on when the parsing would fail. For that I need to breakup the parsing processing in chunks as the text field doesn’t refresh (even with invalidDisplayList) during intensive processing.
Please keep me informed how the apps work (on Windows, on Linux, size of log files).
Justin Dossey
Wed, 27 Feb 2008 18:26:23 GMT
The reason large files are not loading is the line count—268427264 is some integer limit, I’d bet. 256 * 1024 * 1024.
The log visualizer seems to fail on a 250M logfile =(
Very good job. That is quite impressive given the complications of the transport. It looks easier to use.
The very first version of the log visualizer was using not an AIR application, it was a Flex front-end with a Ruby log file parsing and was able to process larger log files (i.e. 4gb in 10minutes), I haven’t tried with such large files since I am now “rollling” the logs and analyze smaller log files. Also I couldn’t get the feedback/progress of the parsing to refresh the display which would give a good indication on when the parsing would fail. For that I need to breakup the parsing processing in chunks as the text field doesn’t refresh (even with invalidDisplayList) during intensive processing.
Please keep me informed how the apps work (on Windows, on Linux, size of log files).
The reason large files are not loading is the line count—268427264 is some integer limit, I’d bet. 256 * 1024 * 1024.
Scratch that—it’s a byte count.
That does look user friendly. I will give it a try tomorrow. Thanks for sharing.