Provide better information regarding memory usage by each plugin

[mgazdzik]

In some cases archiving process is crashing because of reaching memory limit.
It's not always possible to just increase RAM limit for PHP process.
Therefore it would be a good to have reusable diagnostic tool, telling which plugin is depleting limit so it can be improved.

Goal of this ticket is to discuss such tool specification (possible usage, reported data, etc.) and implement it in core.

[mattab]

Also to note this particular problem occurs for period=year

2014-11-20 17:40:20 ERROR [2014-11-20 17:40:20] [a1988] Got invalid response from API request: index.php?module=API&method=API.get&idSite=1&period=year&date=last2&format=php&token_auth=x&trigger=archivephp. Response was 'PHP Fatal error: Allowed memory size of 4294967296 bytes exhausted (tried to allocate 8208 bytes) in /srv/piwik/piwik-2.8.3/core/DataTable.php on line 1156 '

[czolnowski]

@mgazdzik I suppose that you need this information in archiving output. Since there is running API.get then might be difficult to gather information for every plugin. Would be enough to gather memory peak for every period & segment?

[mgazdzik]

@czolnowski - why would it be difficult ? All plugin archivers are being triggered one after another in a loop, so I think it would be sufficent to store memory usage before and after archiving of single plugin and print it out. As for periods and segments - sure, this information could also be very useful. Maybe periods + segments could be on debug level, and per plugin on verbose ?

[mattab]

Hi @czolnowski if it's done please close that one 👍

[czolnowski]

@mattab: I'm not sure how can I do this. There should be close button next to comment, but... I think that I don't have access to this repository.

[mattab]

@czolnowski you should now be able to close tickets! Welcome to the Piwik organisation.

[mattab]

Hi @czolnowski I closed it as it looks fixed! 👍