-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Archive.php memory improvements (up to 10 times less memory required!) #4604
Copy link
Copy link
Closed
Labels
CriticalIndicates the severity of an issue is very critical and the issue has a very high priority.Indicates the severity of an issue is very critical and the issue has a very high priority.TaskIndicates an issue is neither a feature nor a bug and it's purely a "technical" change.Indicates an issue is neither a feature nor a bug and it's purely a "technical" change.c: PerformanceFor when we could improve the performance / speed of Matomo.For when we could improve the performance / speed of Matomo.
Milestone
Description
Metadata
Metadata
Assignees
Labels
CriticalIndicates the severity of an issue is very critical and the issue has a very high priority.Indicates the severity of an issue is very critical and the issue has a very high priority.TaskIndicates an issue is neither a feature nor a bug and it's purely a "technical" change.Indicates an issue is neither a feature nor a bug and it's purely a "technical" change.c: PerformanceFor when we could improve the performance / speed of Matomo.For when we could improve the performance / speed of Matomo.
At InnoCraft we are running Piwik for large and very large websites and have identified challenges in memory usage during pre-processing of report data.
The goal of this ticket is to investigate with XHProf profiler, and find the cause of these memory issues and fix them.
Archiving memory required before investigation started: 8Gb.
Memory after the ticket is implemented: 1Gb.
THE POWER OF BETTER CODE. NO LEAK.