@diosmosis opened this Issue on October 27th 2012 Member

Most of Piwik when archiving will generate DataTables and then apply a sort and truncation filter before storing them as records. This is highly inefficient when dealing w/ DataTables w/ thousands of rows, since every one of those rows will have to be first allocated & constructed then sorted.

As done in the Actions plugin it is possible to apply ordering through the SQL and then use new DataTable functions to limit the number of rows in a DataTable w/o having to create and sort every possible one. This technique should be used everywhere possible.

@mattab commented on December 15th 2012 Member

It should be used for all reports that are bigger than normal: Custom Variables, Geoip reports, Actions, Referrers.

@anonymous-matomo-user commented on February 11th 2013

When will you start on this? Is there some more documentation to possibly patch this ourselves?

@mattab commented on February 11th 2013 Member

Not planned at this stage as we lack resources. You are welcome to sponsor this work if you want to get it done, or send a patch....

@anonymous-matomo-user commented on February 12th 2013

What would the sponsorship cost?

@mattab commented on February 14th 2013 Member

Get in touch for more info at matt@piwik.org or http://piwik.org/consulting/

@mattab commented on March 30th 2015 Member

This issue was fixed in 2.12.0!

This Issue was closed on March 30th 2015
Powered by GitHub Issue Mirror