Opened 2 years ago

Closed 23 months ago

#3140 closed Bug (fixed)

API Performance improvements on very large setup: SQL query tweak

Reported by: matt Owned by:
Priority: normal Milestone: Piwik 1.8
Component: Core Keywords:
Cc: Sensitive: no

Description

See in forum

We could change the archive select sql query to make it faster and use an index instead of memory sort.

Attachments (1)

3140.diff.tar.gz (3.6 KB) - added by capedfuzz 2 years ago.
Benchmarking patch.

Download all attachments as: .zip

Change History (4)

Changed 2 years ago by capedfuzz (diosmosis)

Benchmarking patch.

comment:1 Changed 2 years ago by capedfuzz (diosmosis)

Been looking into this issue. I created a benchmarking system to test the changes I made. However, there doesn't seem to be any change in speed when applying the changes SQL changes specified in the forum... Maybe I'm not adding enough data?

comment:2 Changed 2 years ago by matt (mattab)

Nice that you investigate this one, it's not easy to reproduce such issues indeed.

  • Did you try on mysql 5.5.x ?
  • in the bug report the user had about 1M rows in the tables, so maybe the bug shows up with more?
  • Also you can try changing the tables to InnoDB which might be one factor playing a role in this regression?

comment:3 Changed 23 months ago by matt (mattab)

  • Resolution set to fixed
  • Status changed from new to closed

(In [6402]) Fixes #3140 Can it really be that simple??

Note: See TracTickets for help on using tickets.