5 ms·

> Matomo is decent, but my main issue with it is the performance when run at any sort of scale. It's PHP/MySQL, which is nice for ease of self-hosting, but it m

> Matomo is decent, but my main issue with it is the performance when run at any sort of scale. It's PHP/MySQL, which is nice for ease of self-hosting, but it means a lot of things need to be pre-calculated. I've never actually run into performance issues, neither when using it in production professionally, nor for my self-hosted sites (with Matomo always running on-prem). I'd say the performance of PHP and MySQL/MariaDB is most likely decent as long as you don't go too far into specialized workloads, for example log aggregation/tracing; though even some APM solutions like Apache Skywalking also support using traditional RDBMSes for this purpose as well: https://skywalking.apache.org/docs/main/v9.0.0/en/setup/backend/backend-storage/#mysql https://skywalking.apache.org/docs/main/v9.0.0/en/setup/back... That said, I can't help but to wonder at what actual scale (number of logged events/second, given certain hardware) you'd run into issues. Luckily, because adding basic analytics is usually quite easy, testing this for your own workloads shouldn't be out of the question - then you can let the data speak for itself.

jhpacker 4y ago
The performance issues aren't with the measurement requests but with reporting. When I eval'd it for my book last fall there were big delays in reporting waiting for segments and then also issues with custom reports. I think they have changed the default behavior to get around some of the former, but with MySQL it's always going to be tough for larger queries. (if there's any performance issue on the measurement side it has more to do with the JavaScript payload because they include a lot in their standard JS bundle).
- deleted 4y ago
  [deleted]
- unmole 4y ago
  > with MySQL it's always going to be tough for larger queries MySQL was too slow for running analytics on a single website? How much data are we talking about?
  - jhpacker 4y ago
    For self-hosted, if you are doing into the tens of thousands of pageviews per day you may want to turn off real-time and switch to auto-archiving which pregens reports. That level of traffic depends a lot though on the report period you are running against and how big you've provisioned your MySQL server. YMMV and I haven't benchmarked at multiple traffic levels.

jhpacker 4y ago

The performance issues aren't with the measurement requests but with reporting. When I eval'd it for my book last fall there were big delays in reporting waiting for segments and then also issues with custom reports. I think they have changed the default behavior to get around some of the former, but with MySQL it's always going to be tough for larger queries. (if there's any performance issue on the measurement side it has more to do with the JavaScript payload because they include a lot in their standard JS bundle).

deleted 4y ago
[deleted]
unmole 4y ago
> with MySQL it's always going to be tough for larger queries MySQL was too slow for running analytics on a single website? How much data are we talking about?
- jhpacker 4y ago
  For self-hosted, if you are doing into the tens of thousands of pageviews per day you may want to turn off real-time and switch to auto-archiving which pregens reports. That level of traffic depends a lot though on the report period you are running against and how big you've provisioned your MySQL server. YMMV and I haven't benchmarked at multiple traffic levels.