apurtell edited a comment on pull request #3244:
URL: https://github.com/apache/hbase/pull/3244#issuecomment-837051331


   **WAL Compression Results**
   
   Site configuration:
   
       <!-- retain all WALs  -->
       <property>
          <name>hbase.master.logcleaner.ttl</name>
          <value>604800000</value>
       </property>
   
       <!-- to enable compression -->
       <property>
           <name>hbase.regionserver.wal.enablecompression</name>
           <value>true</value>
       </property>
   
       <!-- to enable value compression -->
       <property>
           <name>hbase.regionserver.wal.value.enablecompression</name>
           <value>true</value>
       </property>
   
   IntegrationTestLoadCommonCrawl
   Input: 
s3n://commoncrawl/crawl-data/CC-MAIN-2021-10/segments/1614178347293.1/warc/CC-MAIN-20210224165708-20210224195708-00000.warc.gz
   
   | Mode | WALs aggregate size | Difference |
   | -- | -- | -- |
   Default | 5,006,963,824 | - |
   Compression enabled, value compression not enabled | 5,006,874,201 | (0.1%) |
   Compression enabled, value compression enabled | 940,657,251 | (81.2%) |
   
   In this test case WAL compression without value compression is not enough. 
The schema is already optimized for space efficiency: column families and 
qualifiers are single characters. There is a bit of redundancy that can be 
reclaimed but the bulky values (web crawl results) dominate. 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Reply via email to