Huge performance drop #4285
Unanswered
rickytato
asked this question in
Self-Hosted Support
Replies: 2 comments 13 replies
-
There haven't been any major changes in how Plausible uses ClickHouse from v2.0.0 to v2.1.1, so I can't think of anything that could cause this off the top of my head. You might be able to use system.query_log to find the problematic queries in v2.1.1 and compare them with v2.0.0 counterparts, you might be able to filter by |
Beta Was this translation helpful? Give feedback.
3 replies
-
@ruslandoga actually, we revert the installation, we are on production, so I can't see slow query log for the new installation. |
Beta Was this translation helpful? Give feedback.
10 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi, we tried to upgrade from v2.0.0 to v.2.1.1 (v2.1.0 -> v2.1.1) but we had to revert (restoring from backup) because is unusable.
Clickhouse use all 16core and 32GB of RAM (we also tried to increase to 64GB).
We are on our hardware, with AMD EPYC and NVMe , so we have no "cloud" problems.
With v2.0.0 all work perfectly but with v2.1.1 we are unable to see stats greather than one month, Clickhouse explode; with v2.0.0 dashboard show data from last year in near realtime.
Beta Was this translation helpful? Give feedback.
All reactions