Contributors mailing list archives


Re: Idea for performance improvement

LasLabs, Dave Lasley
- 09/10/2017 20:56:36
I think this is a great idea as well. Monkey patching is totally not necessary I think though- as long as the problems are happening in a model, we can delay the method with a few lines of code. 

Along what Raphaël said though- I think the hardest part will just be identifying the bottlenecks. 

-Dave Lasley

On Oct 9, 2017, at 11:32, Raphaël Valyi <> wrote:

I suggested the same when these social features were introduced back in v7, so yes I think it could help. Curious if that can be overriden or monkey patched though. During the Odoo Experience, Antony Lesuisse also confirmed me these tracking things were the things generating most requests when creating/updating records... Would be worth checking the number of SQL requests when creating say a sale order vs patching Odoo to remove the social mixin and checking again...

On Mon, Oct 9, 2017 at 8:17 PM, Graeme Gellatly <> wrote:
Hi all,

I was just looking through the 'performance' improvements.

Essentially they mostly come down to 2 things - removal of workflow, and removal of tracking in specific cases.

So I had the idea, if tracking is so performance hungry, could we in OCA not just make a small module that basically uses Queue on Social features?

I actually did a little POC, combining report printing with queue. This case is in automated actions, but actually the original POC used any report sent directly to a printer. 

Discussion here:

Because it takes a few seconds to render a pdf, but the user doesn't know if the delay is just the usual printing delay or not, they just get back screen back instantly.  I think the same concept applies to tracking/sending email in a lot of cases,  User won't worry about tracking messages not showing up immediately?

Post to:

Raphaël Valyi
Founder and consultant