Reputation
Top tag
Next privilege 200 Rep.
See reduced ads
Badges
10
Impact
~5k people reached

  • 0 posts edited
  • 0 helpful flags
  • 13 votes cast
Sep
16
comment Composite index works for larger set of data, but not smaller
Comments on this question have been moved to chat.
Sep
16
revised Composite index works for larger set of data, but not smaller
added 1270 characters in body
Sep
16
comment optimise my.ini for key query
the varchar was a mistake in the question posted above. At this point I tried this solution dba.stackexchange.com/a/4192/2599. I did forget change the definition of is_intensive back to tinyint. I have limited the amount of columns now, which did help, but not dramatically. Have posted a fllow up question here dba.stackexchange.com/q/115165/2599
Sep
16
asked Composite index works for larger set of data, but not smaller
Sep
11
accepted optimise my.ini for key query
Sep
9
comment optimise my.ini for key query
I can remove ordering, but have to add more client side code. I need it ordered, but output is paged. Will also remove paging count query
Sep
9
comment optimise my.ini for key query
I have added explain statement. I have also changed query slightly to display slower case where is_intensive is 1. In my opinion this should be faster as is_intensive=1 is a smaller data set.
Sep
9
revised optimise my.ini for key query
add explain statement, reformulate query
Sep
9
comment optimise my.ini for key query
INDEX(is_intensive, status_id) brings it from 9000ms to ca 900ms!
Sep
9
comment optimise my.ini for key query
70% of RAM also on an Apache/Mysql shared machine?
Sep
8
asked optimise my.ini for key query
Feb
20
comment Multiple relationships issue
Did you have a chance to dissect it and accept the answer?
Feb
20
accepted Speed efficient query for membership first joined, latest category from membership table (min, max)
Feb
20
accepted MySQL optimize range duplicate query
Nov
10
answered MySQL optimize range duplicate query
Nov
10
comment MySQL optimize range duplicate query
@Manny, tried this, but no change. I did not expect this to hav any effect as existing indexes were already used, but the resultset was still too big
Nov
7
asked MySQL optimize range duplicate query
Jul
1
awarded  Popular Question
Mar
3
awarded  Student
Oct
19
answered Moving large databases