So, looking at my not-even-100-day old, 2.8GB "~/Library/Application Support/Linkinus 2/Logs.lnk2Log" logs file with MesaSQLite, I see, among other things:
6 ZLOGNETWORK records
298 ZLOGCHAT records
2100 ZLOGSESSION records
1523541 ZLOGLINE records (that I can't even list, because the table is way too big)
Now, look at all the stuff that's stored for each ZLOGLINE record:
http://gyazo.com/f6cee647c70a22f14da407ec6349f079.png
For example, this 41 character line of text: "[12:39] <Cowboy> looks like 1.5m records" is stored in the DB as 302 chars of binary data, plus a 59-character GUID and a few other indices.
Now, I don't know about you, but while it's nice to view logs all fancy-like, usually all I want to do is search through them.. and having over 361 chars (or *8* times as much data as is really necessary) stored in this complex data structure, crashing Linkinus every time I try to search, is not really helping me much.
Not to mention that for 1.5 million lines, all this extra overhead really adds up, and I've got a not-insubstantial chunk of my hard drive eaten up by a file that I can neither split nor incrementally backup.
I'm personally all for simple, plain-text logs.. but I understand how fancy-looking logs can be cool too. Still, after just a few months, I'm stuck with a logging system that is almost completely unusable, which is just no good.
I think it's time for a better solution!
- Ben

resolved by our support staff or its poster.
Reply
You must log in to post.