phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ankit Singhal (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-3559) More disk space used with encoded column scheme with data in sparse columns
Date Wed, 04 Jan 2017 08:25:58 GMT


Ankit Singhal commented on PHOENIX-3559:

I did some comparison earlier with table having all data types(except array) with dense records.
Posting here, if it can save some [~mujtabachohan] efforts.

|UPSERT|25.295 sec|47.315 sec|46.779 sec|
|COUNT|5.95 sec|7.719 sec|7.91 sec|
|No compression(AFTER COMPACTION)|183M|182M|182M|
|GZ(compression ratio)|38M(4.32:1)|44M(2.75:1)|41M(2.95:1)|
|Snappy(compression ratio)|50M(2.42:1)|56M(2.16:1)|56M(2.16:1)|

PHOENIX-2565 vs RowkeySchema

||Encoding(input data size=111M)||	Phoenix(Single KV PHOENIX-2565)||Phoenix With new Encoding(like
|No compression(encoding ratio)	|143M(1:0.77)|95M(1.16:1)|
|Snappy( compression ratio)	|51M(2.17:1)|	46M(2.41:1)|

> More disk space used with encoded column scheme with data in sparse columns
> ---------------------------------------------------------------------------
>                 Key: PHOENIX-3559
>                 URL:
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: Mujtaba Chohan
>            Assignee: Samarth Jain
>             Fix For: 4.10.0
> Schema with 5K columns
> {noformat}
> create table (k1 integer, k2 integer, c1 varchar ... c5000 varchar CONSTRAINT PK PRIMARY
KEY (K1, K2)) 
> {noformat}
> In this schema, only 100 random columns are filled with random 15 chars. Rest are nulls.
> Data size is *6X* larger with encoded columns scheme compare to non-encoded. That is
12GB/1M rows encoded vs ~2GB/1M rows non-encoded.
> When compressed GZ, size with encoded column scheme is still 35% higher.

This message was sent by Atlassian JIRA

View raw message