Log Viewer is slow with large chat logs - Printable Version -Shoutbox (https://shoutbox.menthix.net) +-- Forum: MsgHelp Archive (/forumdisplay.php?fid=58) +--- Forum: Messenger Plus! for Live Messenger (/forumdisplay.php?fid=4) +---- Forum: WLM Plus! General (/forumdisplay.php?fid=23) +----- Thread: Log Viewer is slow with large chat logs (/showthread.php?tid=81528) Log Viewer is slow with large chat logs by garreh on 02-08-2008 at 10:05 PM
Decrypting a log file which is 2.75MB takes an agonising 26 seconds. It's the 8th -- and I dare think what the log file size will be by the end of the month, and how long the LogViewer will take to show me the log! RE: Log Viewer is slow with large chat logs by Patchou on 02-08-2008 at 10:11 PM well, it shouldn't take that long... it depends on your system specs really. All I can suggest is to decrease the encryption key size (preferences), that's what will make the most difference (for future generated log files). RE: Log Viewer is slow with large chat logs by garreh on 02-08-2008 at 10:24 PM
Thanks for your reply Patchou. RE: Log Viewer is slow with large chat logs by Matti on 02-09-2008 at 09:27 AM
Basically, encrypted log files are HTML files which were encrypted by Plus! Live. When Plus! opens the log file, it checks the given password by decrypting a known signature in the log file and if that result matches the original signature, it decrypts the whole log file and stores it in a temporary location. Then, it loads that file in the Log Viewer window. In fact, you can encrypt any type of file with the Plus! encryption, and it'll work perfectly fine. RE: Log Viewer is slow with large chat logs by garreh on 02-09-2008 at 02:52 PM
Thanks for your reply Mattike. quote: RE: Log Viewer is slow with large chat logs by Patchou on 02-13-2008 at 06:29 PM Ziping before encrypting could be a good idea, the problem however is that logs, by nature, are ever growing files. Compressing each block in the file could be prone to error and cause many differnt kinds of problems. Still, I'll keep that in mind. RE: Log Viewer is slow with large chat logs by garreh on 02-13-2008 at 10:06 PM
Yes, Patchou -- This is the problem with zipping. However, even now, without much change, filesizes could be reduced by over half in most cases... code: This line could be reduced to simply... code: So what did I do? 1: Replaced <span class="time"> to <i> and also replaced the CSS entry .mplsession table th span.time {color:#949494;font-weight:normal;} with... code: 2: Replaced style="X" with class="a" ... How this works is by adding an entry to CSS like so... code: a relates to one persons colour, and b for another, more can be added obviously like c, d, e, f, .... you get the picture. A simple function could be made AddCssColour(<css code>) and simply use base 26 to increment. Then GetCurrentCssColour(<contact id>) to get the CSS class name. I also removed trailing spaces and newlines, which removes a further 4 bytes for every line, which would amount to 23KB of pure junk over 6000 lines, why not? ------------- Using these simple changes: Original filesize: 2.13MB New, reduced filesize: 1.16MB - 54% reduction! Not only would files load twice as quick, it would reduce amount of data in memory, amount being written to disk and increase encrypting and decrypting speed. These changes wouldn't affect old log files, but I think could easily be incorporated to improve future versions of Plus! RE: Log Viewer is slow with large chat logs by Patchou on 02-13-2008 at 10:52 PM you just can't add this kind of thing in html logs... remember that log files grow, the header, once written in the file, cannot be changed. RE: Log Viewer is slow with large chat logs by ahmetgns on 02-29-2008 at 12:01 AM
By the way, I found an annoying thing which may grow html files rapidly. code:As you see, there are two bold information when not needed. I know, noone inserts tags like that. However the important thing is if user give a gradient effect to his messages with other formatting like bold or italic, then these bold and italic informations are written in html files for each letter.For example, if user sends a message like[b][c=4]Hello my contact[/c=8][/b] then the result in html file is code:This problems arises in nicknames mostly, because people can give formats other than gradient effect to their messages from original Messenger's font option (and this will not cause this duplicate entry problem for each letter) but for display names if people make their name bold&italic&underlined and give a gradient color, then for each letter, the bold&italic&underlined infos are written seperately. And this is unnecessary I think. If possible, please optimize logging of texts formatted like that. |