[drupal-devel] MySQL, large keys
herman.webley at gmail.com
Fri Oct 21 12:10:00 UTC 2005
On 10/21/05, Moshe Weitzman <weitzman at tejasa.com> wrote:
> you are optimizing selects that are already very very fast. these are single
> table queries with a single condition on an indexed column.
> i think that further optimizing drupal for the mysql query cache is a more
> involved effort. you have to simplify queries in order to avoid DISTINCT(),
> COUNT(), SUM(), etc. that often means performing subqueries or multiple
> successive queries.
> with mysql query cache enabled, i am seeing pages using 50ms of total query
> time. not much to improve upon IMO.
I think the point here is that the fast (50ms) queries occur on a
cache hit. Splitting the cache table would increase the probability of
cache hits as the entire cached data set won't be invalidated for
every cache change.
More information about the drupal-devel