[HBASE-5778] Fix HLog compression's incompatibilities

• Type: Improvement
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 0.94.4, 0.95.0
• Hadoop Flags: Reviewed
• Assignee: Jean-Daniel Cryans
• Reporter: Jean-Daniel Cryans
• Created: 12/Apr/12 22:17
• Updated: 04/Sep/13 00:14
• Resolved: 21/Dec/12 05:59

Description

I ran some tests to verify if WAL compression should be turned on by default.

For a use case where it's not very useful (values two order of magnitude bigger than the keys), the insert time wasn't different and the CPU usage 15% higher (150% CPU usage VS 130% when not compressing the WAL).

When values are smaller than the keys, I saw a 38% improvement for the insert run time and CPU usage was 33% higher (600% CPU usage VS 450%). I'm not sure WAL compression accounts for all the additional CPU usage, it might just be that we're able to insert faster and we spend more time in the MemStore per second (because our MemStores are bad when they contain tens of thousands of values).

Those are two extremes, but it shows that for the price of some CPU we can save a lot. My machines have 2 quads with HT, so I still had a lot of idle CPUs.

Issue Links

• is related to: HBASE-4608 HLog Compression
• relates to: HBASE-6533 [replication] replication will block if WAL compress set differently in master and slave configuration