feat(clickhouse-driver): allow to enable compression

[Graphmaxer]

Check List

• Tests have been run in packages where changes made if available
• Linter has been run for changed code
• Tests for the changes have been added if not covered yet
• Docs have been added / updated if required

Issue Reference this PR resolves

Description of Changes Made

Allow to enable compression via env variable for clickhouse driver

[Graphmaxer]

Thanks for the comments, I also updated the clickhouseReadOnly option to the new env-var way :)

[igorlukanin]

Before we merge this—

@Graphmaxer Did you confirm that enabling the compression actually improves the performance for large result sets?

[igorlukanin]

Also, if this is a non-breaking change (except for the nuance with read-only connections), should we consider enabling the compression by default in the next minor version of Cube?

[Graphmaxer]

I did some testing documented in my issue #9340, I got positive impact in my use case. According to the Clickhouse documentation, this can have negative impacts depending on the queries.

The client does not enable request or response compression by default. However, when selecting or inserting large datasets, you could consider enabling it via ClickHouseClientConfigOptions.compression (either for just request or response, or both).
Compression has significant performance penalty. Enabling it for request or response will negatively impact the speed of selects or inserts, respectively, but will reduce the amount of network traffic transferred by the application.

https://clickhouse.com/docs/integrations/javascript#tips-for-performance-optimizations

[maximethebault]

Also facing the same issue when using PowerBI... Queries time out, but when replaying them in Clickhouse directly, they are almost instantaneous.

[Graphmaxer]

Up 😢

[ovr]

Thank you @Graphmaxer for your contribution 👍 🍰

Merged, it will be released in the next release.