Optimizing ClickHouse: Tactics that worked for us(highlight.io) |
Optimizing ClickHouse: Tactics that worked for us(highlight.io) |
I remember wanting to use Heap's session replay only to release they want hundreds of dollars per _month_, my last bill with highlight was $2.38 I recall.
That's all to say that I'm glad Highlight is figuring out how to scale while still offering their features to the small players of the world.
The pages clearly defined what you are building and how to use it.
The explanation of platform fees makes sense, though it could more clear if the pricing examples are only based on those fees or are account limits to number of members or dues.
You might want to check your terms of service, they do not list a jurisdiction and have the placeholder [jurisdiction] instead.
Best of luck with it!
[0] https://clickhouse.com/docs/en/engines/table-engines/special...
Plus, async inserts are only available on ClickHouse Cloud.
Just a heads up, You've got repeated line there
> OTLP
I also like that the blog is quite compact and gets the points across without getting too much into the weeds.
One thing I've noticed also that bloom filter index types can be quite costly to merge. In many cases that's acceptable though due to the massive benefit they provide for text queries. One just has to be mindful of the overhead when adding them.
* Create a new version of the table with the new ORDER BY.
* Create a materialized view that will insert from the old table to the new table.
* Update your application code to query the new table.
* Start inserting data into the new table.
To enable asynchronous INSERTs, set `async_insert` to true.
Here is the documentation: https://clickhouse.com/docs/en/optimize/asynchronous-inserts ; intro: https://clickhouse.com/blog/asynchronous-data-inserts-in-cli... and a hands-on guide: https://clickhouse.com/blog/monitoring-asynchronous-data-ins...