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

Posted to issues@trafficserver.apache.org by "Zhao Yongming (JIRA)" <ji...@apache.org> on 2013/09/25 12:32:03 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=13777335#comment-13777335 ] 

Zhao Yongming commented on TS-1521:
-----------------------------------

questions on how to implement:
1, should we enable gzip on client side? can we gzip on the collation side before farwording? in case the collation server is in the localnetwork and cache server heavy load
2, should we gzip in ET_NET threads? is ET_TASK a good option?
3, can we forward the gziped log on collation server?
                
> 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
>            Assignee: Yunkai Zhang
>             Fix For: 5.0.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