3 ms·
Not sure why you are downvoted. One of the biggest concerns about any DB is speed of query execution. Today a decent app/site can generate terabytes of machin
by zooq_ai 2y ago
Not sure why you are downvoted.
One of the biggest concerns about any DB is speed of query execution.
Today a decent app/site can generate terabytes of machine data that you need to analyze.
There is a massive difference in usability of a query that takes < 5 secs vs even 5 minutes. So, some benchmarks of speed vs major use cases would have been ideal.
I understand, general purpose DBs can't be the best, but I can compromise for 80%. If it's 50% or less, then I really have to question that choice.
- jamesgresql 2y ago(Author here!) I'd compare performance to what you need, not to other technology. But also, point taken. The article this comment thread describes also needs to be written.
- simonw 2y agoIf you're generating terabytes of analytical data you should be using a different stack for analyzing that than you do for running your production workload. (You could still use PostgreSQL, just not the same PostgreSQL servers that are running your user-facing features.)
- zooq_ai 2y agoThat's my point. If Postgres is only 60% performant compared to Clickhouse, I have no choice but to go with Clickhouse.