Speed on larger datasets.

[plezploz]

I've noticed the application lag quite a lot when loading up all time statistics for websites (ex. umami's own demo https://app.umami.is/share/8rmHaheU/umami.is). Could this be possibly solved by adding some running counters for large sections of data?

[franciscao633]

Our cloud product uses Clickhouse, which doesn't have issues with the large datasets. However we are aware of performance issues in our self-hosting options (postgres/mysql) with larger datasets and explored options like TimescaleDB. We are open to other solutions as well and trying to balance performance with having as little dependencies to run Umami as well.

[icexuick]

Is there some info on what hardware a proper server needs to run Umami well on larger datasets.
We have some trackers with over 1M pageviews per month, and we can only use 7 days overviews - 30 days and higher crashes the server.

We use PHP/sql, currently on a 1 core 2GB ram server.
Should we upgrade to 2 cores/4GB or even 4 cores/8GB ?

[Matthijz98]

Can the self hosted version also use clickhouse?
Or do you just use the Postgres connector from clickhouse?

[franciscao633]

Currently not. Need to make some updates to write directly to CH, roll out some docs, setup, etc. The code is like 90% there to self-host a CH version of Umami.

[marcfowler]

I'd be very keen to see the Clickhouse version. Is there anything we can do to help get that over the line?

[wc-matteo]

same

[icexuick]

Does anybody have more information on better performance on self-hosting?
We have a site which gets between 1-2M pageviews per month, but we can only use the "7 day" overview. On "30 days" most of the data/graphs don't load anymore, and it crashes on "90 days".

We have tried cloud.umami for a month and a half, with over 1.3M page views, and that loads super-fast / instantly.

Any help / feedback / tips on how to get this working on a self-hosted solution is very much welcome!

[CammerJack]

what is considered large dataset? When it will start slowing down?