Categories
- Ruby On Rails (80)
- Playground (6)
- Rails Tips (14)
- Time.OnRails.org (9)
- Ruby (23)
- Business (2)
- Flex (44)
- iPhone (2)
Screencasts
Archives
- July 2010 (1)
- June 2010 (2)
- May 2010 (1)
- April 2010 (5)
- March 2010 (10)
- February 2010 (2)
- November 2009 (1)
- October 2009 (2)
- September 2009 (2)
- August 2009 (1)
Our Applications
Our Book
HOTIt's Here!
Related Blogs and Friends
Syndicate


about 4 hours later
The log visualizer seems to fail on a 250M logfile =(
about 7 hours later
Very good job. That is quite impressive given the complications of the transport. It looks easier to use.
about 8 hours later
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).
1 day later
The reason large files are not loading is the line count— 268427264 is some integer limit, I’d bet. 256 * 1024 * 1024.
1 day later
Scratch that— it’s a byte count.
2 days later
That does look user friendly. I will give it a try tomorrow. Thanks for sharing.