[Tickets #9342] Re: using an index on horde_cache table improve performance

[bugs at horde.org]

BITTE NICHT AUF DIESE NACHRICHT ANTWORTEN. NACHRICHTEN AN DIESE  
E-MAIL-ADRESSE WERDEN NICHT GELESEN.

Ticket-URL: http://bugs.horde.org/ticket/9342
------------------------------------------------------------------------------
  Ticket           | 9342
  Aktualisiert Von | michael at bigmichi1.de
  Zusammenfassung  | using an index on horde_cache table improve performance
  Warteschlange    | Horde Framework Packages
  Version          | FRAMEWORK_3
  Typ              | Enhancement
  Status           | New
  Priorität       | 1. Low
  Milestone        |
  Patch            |
  Zuständige      |
------------------------------------------------------------------------------


michael at bigmichi1.de (2010-10-24 04:17) hat geschrieben:

i suggest a primary key index on 'cache_id'

and my optimizer tool also suggest:


./qot --input-file=input.sql --input-query="SELECT cache_data FROM  
horde_cache WHERE cache_id = '7af43c8a03e4cb392e9798b9c259e9d5' AND  
cache_timestamp >= 1287901202;" --info --propose=index
/* Output produced by qot 0.0.4 GPL */
/*
Query: SELECT cache_data FROM horde_cache WHERE cache_id =  
'7af43c8a03e4cb392e9798b9c259e9d5' AND cache_timestamp >= 1287901202

   selectivity:
     zero or one row

   used tables:
     horde_cache (zero or one row)

   ordering:
     no ordering

   existing lookup indexes:
     horde_cache.PRIMARY(cache_id)

   existing covering indexes:
     (none)
*/
/* additional lookup indexes that can be created to improve query  
performance */
CREATE UNIQUE INDEX index0 ON `qot_test`.`horde_cache` (
   cache_id,
   cache_timestamp);



the tool i used is QOT http://ritmark.com/, perhaps you can verify the result