Conceited Forums RSS Feed

1. 

   'Cowboy' Ben Alman
   Member

   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

   Simplified - http://benalman.com/projects/simplified-style/
   http://benalman.com/grab/5bfaef.png :D

   Posted 2 years ago #
2. 

   'Cowboy' Ben Alman
   Member

   For what it's worth, I executed this script (I'm sure there's a better way to do it) to see what my text log sizes were like under Linkinus 1.x:

   
cd ~/Documents/Linkinus\ Logs && echo $(find . -iname '*.txt' -exec stat -f%z '{}' + | perl -p -e 's/[\s]+/ + /;s/$/0/') | bc


   It output 778651719, or 0.7gb of easily-searchable text logs for 11 months of Linkinus 1.x usage.

   At the rate Linkinus 2.x is going now, after 11 months of usage I'll have a single, completely unsearchable, 9.5gb Logs.lnk2Log file.

   - Ben

   Posted 2 years ago #
3. 

   ohkine
   Member

   I completely agree and have mentioned this several times before in other threads and bug reports. The log system Linkinus has now is attractive, but as you mentioned the size of the files is outrageous, plus the logs are now inaccessible by grep, pisg, eggdrop, &c. An option to export to plain text was added in 2.0.1, but at the risk of sounding ungrateful i think it's almost completely worthless, because you can only do it one session at a time, and it's incredibly slow.

   The log viewer in general is really really slow, actually — depending on the size of the particular log you're trying to view and how long you've been keeping logs, it can take 2 or 3 full minutes just to open a single log session (never mind actually browsing through it, exporting it, or switching between logs), which is obviously not ideal.

   Posted 2 years ago #
4. 

   pkevin
   Member

   The log system is by far the weakest point in Linkinus. Said it so many times. Plus I'd really need the ability to search through my old Linkinus 1.x logs now.

   Posted 2 years ago #
5. 

   Okeanos
   Moderator

   You should be able to search through them, still. They are html logs, nothing fancy.

   Posted 2 years ago #
6. 

   karmacoma0
   Member

   Couldn't agree more, it´s very important to have good logging abilities and sadly, the current logging in linkinus sucks. I had to thrash all my logs a while back just to make linkinus even start again. :(

   Posted 2 years ago #
7. 

   Okeanos
   Moderator

   How large were they? I don't have any particular problems out of the usual with a 10GB file.

   Posted 2 years ago #
8. 

   Nicolas
   Co-founder & Developer

   Linkinus 2.1 is now available in the beta program have provides two features to fix this problem:
   - plain text logging
   - automatic rich text logs pruning after x days

   Rich-text logging has also been revamped to take up less hard disk space.

   --
   Nicolas Lapomarda
   Conceited Software

   Posted 2 years ago #

© 2010 Conceited Software. All rights reserved.

• About Us
• Contact Us