Community mailing list archives

Re: sales order confirmation v9: speed issue

Open For Small Business Ltd, Graeme Gellatly
- 02/02/2016 16:55:50
 Hi Nhomar,

I think the improvement will depend with upgrading postgres.

If you are running 9.3 then that database would be a couple years old.  Merely the process of updating, compressing pages, and recreating indexes would account for a little of that.  Far more than any regular full vacuum, which seems to save disk space at the expense of slightly slower queries. As an example our database went from 31GB to 20GB on disk with the upgrade (attachments in file system).  As always the worst offender was the workflow tables.

The abbreviated keys indexing I imagine will also help massively if you aren't already using something like pg_trgm for indexing varchars and relying on the standard ORM btree created ones.  That would mostly be seen in searching though in large databases, not so much in confirming workflow related documents.

As for the extra workers capability, I think that is going to depend.  We spent a lot of time optimizing postgres and for most transactions have it down to roughly an 80/20 split between python / postgres.  In rough terms then, with a more efficient postgres running even 100% faster you'd be talking a 10% time saving in server processing.  But even a standard database with no extra work on the database is roughly 70/30 so 90% is simply not possible I think unless something is really wrong with your 9.3 postgres setup (or you've skipped the ORM and using SQL for everything).  Allowing for browser response and latency drops that saving even further.  For small databases, or with very few users the savings would be even less.

A check in our historical stats shows that preupgrade we had an average load of roughly 4.0 (12 cores/128GB Ram), post upgrade also 4.0 so extra workers not setting the world on fire.  Postgres response times as a percentage of total transaction times actually appear to have increased slightly although that is likely just because it takes a day or so to fully warm the database so lots of cache misses (65ms vs 71ms / transaction average). 

Anyway once I've got a week or so of full logs I'll see what happens and post again.  The performance stats I really want to see are the improvements with python 2.7.11 and computed gotos.  I'll give that a go next week once I understand what 9.5 really does.

On Mon, Feb 1, 2016 at 7:21 PM, Nhomar Hernández <> wrote:

2016-01-31 22:46 GMT-06:00 Nils Hamerlinck <>:
Can you give us the commit id?

Just informative.

We improve 90% on speed in aaaaaalll our processes just updating db engine to 9.5.

We made huge tests this weekend with huge db's and all works like a charm

All over v8.0

The speed improvements are not related to Odoo itself, we didn't apply any update. Psql 9.3 had problems on performance blocking some tables.....

Regards. (Working on update our production environments now....)

Saludos Cordiales

CEO at Vauxoo Odoo's Gold Partner.
Nhomar Hernandez

Post to: