3 ms·
"Imagine having to go through 2.5GB of log entries from a failed software build — 3 million lines — to search for a bug or a regression that happened on line 1M
by gridlockd 6y ago
"Imagine having to go through 2.5GB of log entries from a failed software build — 3 million lines — to search for a bug or a regression that happened on line 1M."
If your build log files approach gigabytes in size, what you're going to need to do is not search for that bug. You're going to need to rethink your career and life choices. You're going to need to take a vacation, do some traveling, get some perspective. Figure out where it all went wrong and what to make of the years that remain. Life is short.
- Datenstrom 6y agoOr just use grep? Are there people building systems that keep logs that are not easily grepable? I've never seen one, and I have seen some very poorly designed systems. I do work outside of traditional environments though (embedded, robotics, avionics).
- vsareto 6y ago>Are there people building systems that keep logs that are not easily grepable? Yeah, I've seen ELK stacks, Splunk, or even RDBMS tables for log entries