c2c-oerpscenario team mailing list archive

["Olivier Dony \(OpenERP\)" <669919@xxxxxxxxxxxxxxxxxx>]

Indices on ir.translations have been reviewed in 6.0, including the
issue with the btree one on the src field.

The new indices are based on the actual queries constructed by the system. Adding more indices is not always a good idea, what is important performance-wise is to have the right indices and also cut down the number of request. We will now work on the latter, as the former is mostly fine from what we can see of the real queries used by a running system.
Keep in mind that postgres can work with partial indices and combine them too.

As Panos notes, we must keep in mind the trade-offs, and a combined
index of 3 columns is already very specific.. if you look at actual
statistics in terms of number of rows you'll see that the combination of
the 4 columns does not give much less results than the combination of 3.

Thanks for the suggestion, and analysis data too! We will be working
with Panos on reducing the number of queries during installation, as
demonstrated in your data.

** Changed in: openobject-server
       Status: New => Won't Fix

-- 
[6.0RC1] request for different indices on ir.translations
https://bugs.launchpad.net/bugs/669919
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.

Status in OpenObject Server: Won't Fix

Bug description:
this 2 indices should improve performance if a lot of translations are to be processed.

    "ir_translation_ltnr" btree (name, lang, type, res_id)
    "ir_translation_ltns" btree (name, lang, type, src)


currently defined only:
 "ir_translation_ltn" btree (name, lang, type)