Finally figured out what was causing the lack of performance on the
partitions with the query. The use of FORCE INDEX was causing the slowdown
with the partitioned table. Once I removed the clause, the query ran in 1
minute 19 seconds, which is more in line with expectations. Sorry for any
inconvenience!
1 comment:
Partha,
I am evaluating a switch from MySQL5.0 to 5.1,( and I found some interesting inputs on your blog. ) and it would be really helpful to me, if you could provide useful inputs in this regard, or point me to the appropriate resource(s).
To briefly explain my situation, I work on building large scale distributed systems that are intended to scale to a few hundred transactions per second. We are seeing progressive degradation of response times with data size, and want to switch to MySQL5.1 for the benefits of Partitioning.
Post a Comment