[Content Bug] Update the compression page

[billy-the-fish]

This page about compression is confusing:
Active chunks are uncompressed and able to ingest data. Due to the nature of the compression mechanism, they cannot effectively ingest data while compressed.
It is now possible to ingest data into compressed chunks and we should clarify that.
Also the image looks very blurry.
image.png

image.png

docs.timescale.comdocs.timescale.com
Timescale Documentation | About compression
How to compress hypertables

New

Ramon
7 hours ago
@Yannis Roussos

Yannis Roussos
7 hours ago
Thank you
@Ramon
, yes we are planning to go through everything once more and fix those inconsistencies..
cc
@matski

@ante
👍
1

matski
7 hours ago
I agree it is confusing. In addition, I would add the uncompressed chunks at the right side since time usually flows from left to right in most diagrams, which would make it more intuitive.
👍
1
💯
1

mike
4 hours ago
Add to
@matski
point, I think we need to maintain consistency. Across most of our illustrations, we show ingest from the left, so older chunks on right.
Regardless of my own preference, my ask is consistency.
Don't use a difference format for this one. (edited)

Emily Kim
2 hours ago
@Iain

@James S
for the consistency note thx!

[mfreed]

Note this is part fo data lifecycle.

SO:

New data -> row-based uncompressed -> column based compressed -> tiered storage