4 ms·
Author here. The limit we hit with ES was the memory required to have anything approaching decent response times for queries. I've always tried to keep ES in me
by Dachande663 4y ago
Author here. The limit we hit with ES was the memory required to have anything approaching decent response times for queries. I've always tried to keep ES in memory but that becomes a pain, and honestly the defaults for CH just... work whereas ES ends up needing a hundred dials slightly tweaked to make it work (and keep working).
The new JSON type looks amazing though! It's probably time I update the code, but honestly it's just been silently chugging along in the background with zero maintenance for now.
- systemz 4y agoMaybe this alternative to ES could help with memory usage? https://github.com/manticoresoftware/manticoresearch https://github.com/manticoresoftware/manticoresearch https://news.ycombinator.com/item?id=34741018 https://news.ycombinator.com/item?id=34741018
- tylerhannan 4y agoAs someone who has worked at both companies (and is at ClickHouse presently), this -- to me -- is the best line I've read this week: "and honestly the defaults for CH just... work whereas ES ends up needing a hundred dials slightly tweaked to make it work (and keep working)." And yeah, that requires an immense amount of focus and effort. Glad you noticed. <3
- jabart 4y agoHow is the compression for these logs for CH?
- deleted 4y ago[deleted]