How about archiving the older logs in a format that may be a one-time CPU expense, but never have to worry about uncompressing? Ie: I don't want really old logs accessible through the UI, but just available by developer request.
Best regards, Alex Ionescu On Mon, Aug 17, 2009 at 2:36 AM, Colin Finck<[email protected]> wrote: > Alex Ionescu wrote: >> Can we please 7zip logs instead of deleting them? > > As the logs are not simple text files, but stored in a database for showing > them together with other test information (see e.g. > http://backend.reactos.org/testman/detail.php?id=341420), I've used MySQL's > COMPRESS/UNCOMPRESS instead of 7-Zip now. > In my opinion, the higher memory requirements and system load of 7-Zip also > don't outweigh the compression ratio for text files, which shouldn't be that > much better compared to a zlib-based algorithm (as it's used by > COMPRESS/UNCOMPRESS). Keep in mind that everybody shall still be able to > easily access these logs over the web interface, so they have to be > uncompressed on-the-fly. > > But all in all, using compression here was a good idea, we're down to 190 MB > now. :-) > > Though I'm still not in favor of keeping logs of ancient revisions forever. > It's okay if we extend the limit to 2-3 years, but does anybody really need > even older logs? > > Best regards, > > Colin > > > _______________________________________________ > Ros-dev mailing list > [email protected] > http://www.reactos.org/mailman/listinfo/ros-dev > _______________________________________________ Ros-dev mailing list [email protected] http://www.reactos.org/mailman/listinfo/ros-dev
