Switching reason · Performance · Causes churn
Moved from Matomo to Umami after hitting scaling limits
1 source thread · first seen 2025-02
Summary
A team hit scaling problems with Matomo even after MySQL tuning and cron archiving, and moved to Umami, which handles their traffic on much smaller instances.
- Affects
- Team running high-traffic instances
- Workaround
- MySQL optimizations and archiving reports through cron
- Switched to or considered
- Umami
Evidence
Excerpts are copied word for word from the source; follow the link to read it in full.
“We recently migrated from Matomo to Umami at work after hitting scaling issues with Matomo”