Where are links supposed to go to? (Just pointing to Piwik PRO website could be maybe improved, maybe a page that shows what kinda options there are re help)

Instead of this approach, Piwik devs should really consider serializing all widgets ajax requests, instead of overloading servers with too many parallel connections. This is not an issue on faster ones, but on budget servers and entry-level shared hosting environments is annoying as hell. I opened this years ago, back when old tracker was used, but it was closed as it could not be reproduced. The main problem is that all widgets load data at the same time, so timeouts occur when server cannot keep up or small timeout is used (sometimes we cannot change this). Again, leaving option in Admin to load widgets in serialized fashion would prevent this from ever happening.

Again, leaving option in Admin to load widgets in serialized fashion would prevent this from ever happening.

Not sure what you mean here?

It should be quite fast even on budget server as long as pre-archiving is enabled and browser-archiving disabled. Even on a kinda budget server. If it is still slow on a budget server with configured pre-archiving, the server is simply too small for the Piwik it is handling. With pre-archived all data is pretty much cached and to retrieve data server is only doing some "quick" lookups.

Hi tseur,

well, all widgets create requests at the same time, which does pose a problem when limited concurrent connections are in effect, or RAM/CPU constraints are hit, and that creates timeout errors because server cannot serve all the requests.

In the meantime, I have done some optimizations (increased concurrent processes limit, piwik's mysql recommended performance tweaks and raised PHP memory to the max), so this has apparently fixed the problem.

But, I have root access in this case, in shared hosting accounts that is not possible, and there are various levels of low / cheap / budget.

If widgets could be loaded one-by-one, that is, wait until first completes loading, then trigger next, then next until last one loads would be ideal. Or, at least add some preset delays before each one starts querying data from the server, to leverage the load.

If widgets could be loaded one-by-one, that is, wait until first completes loading, then trigger next, then next until last one loads would be ideal.

We'd need like a setting for it or detect if an instance is "slow" somehow as for most instances servers are possibly fast enough