You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@trafficserver.apache.org by "Igor Galić (JIRA)" <ji...@apache.org> on 2013/06/28 08:50:20 UTC

[jira] [Commented] (TS-1521) Enable compression for binary log format

    [ https://issues.apache.org/jira/browse/TS-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695294#comment-13695294 ] 

Igor Galić commented on TS-1521:
--------------------------------

it may be generally an advantage to have streaming compression over all types of logs, not just binary logs.
Binary logs take (our) special programs to interpret, whereas plain text can be interpreted by anyone - the gain from streaming compression for logs may give it a performance boost re disk write operations.
                
> Enable compression for binary log format
> ----------------------------------------
>
>                 Key: TS-1521
>                 URL: https://issues.apache.org/jira/browse/TS-1521
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: Logging
>         Environment: RHEL 6+
>            Reporter: Lans Carstensen
>             Fix For: 3.5.0
>
>
> As noted by in a discussion on #traffic-server, gzip can result in 90%+ compression on the binary access logs.  By adding a reasonable streaming compression algorithm to the binary format you could significantly reduce logging-related IOPS.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira