Changes between Version 5 and Version 6 of Database Optimization


Ignore:
Timestamp:
May 10, 2006, 3:53:39 PM (14 years ago)
Author:
earle
Comment:

fix linebreaks

Legend:

Unmodified
Added
Removed
Modified
  • Database Optimization

    v5 v6  
    1 09:24:58  * Dom recommends inspecting http://www.wiki-toolkit.org/browser/wiki-toolkit/trunk/lib/Wiki/Toolkit/Setup[[br]]
    2 09:27:10 <@crschmidt> Dom: the problem is that the metadata table doesn't have a useful index --[[br]]
     109:24:58  * Dom recommends inspecting http://www.wiki-toolkit.org/browser/wiki-toolkit/trunk/lib/Wiki/Toolkit/Setup [[br]]
     209:27:10 <@crschmidt> Dom: the problem is that the metadata table doesn't have a useful index -- [[br]]
    3309:27:52 <@crschmidt> the most common use cases are "Select all metadata for a node, given an id and a version", and "Select all nodes, given a metadata_type and metadata_value"[[br]]
    4 09:28:24 <@Dom> crschmidt: isn't that what, say, http://www.wiki-toolkit.org/browser/wiki-toolkit/trunk/lib/Wiki/Toolkit/Setup/MySQL.pm#L62 is doing?
    5 09:28:52 <@crschmidt> No, that creates a single index -- those can't be split up[[br]]
    6 09:29:07 <@Dom> ah, right.[[br]]
     409:28:24 <@Dom> crschmidt: isn't that what, say, http://www.wiki-toolkit.org/browser/wiki-toolkit/trunk/lib/Wiki/Toolkit/Setup/MySQL.pm#L62 is doing? [[br]]
     509:28:52 <@crschmidt> No, that creates a single index -- those can't be split up [[br]]
     609:29:07 <@Dom> ah, right. [[br]]
    7709:29:51 <@crschmidt> Creating an index on node_id,version would speed up the first case (I Think) and creating an index on metadata_name, metadata_value would speed up the second (I think)
    88