@mattab opened this Issue on May 9th 2012 Member

See in forum

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

@diosmosis commented on May 23rd 2012 Member

Attachment: Benchmarking patch.

@diosmosis commented on May 23rd 2012 Member

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?

@mattab commented on May 24th 2012 Member

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?
@mattab commented on May 30th 2012 Member

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

This Issue was closed on May 30th 2012
Powered by GitHub Issue Mirror