Comment 5 for bug 1233153

Revision history for this message
Raphaƫl Valyi - http://www.akretion.com (rvalyi) wrote : Re: [Bug 1233153] Re: Save partner information gets very slow

Marcel,

from what you tested, the data denormalization itself here is hardly the
issue (it would be if it was making that time like 10x slower). An other
thing you could test, is to see if there are many Ajax requests during this
update. I've already seen that partner form loading slowly after save
because of the dynamic counters of the menu on the left. So monitoring Ajax
calls (your browser has options for that, like CTRL+MAJ+J on Chrome) could
be worth the test. Good luck.

On Tue, Oct 1, 2013 at 9:29 AM, Twinkle Christian(OpenERP)
<email address hidden>wrote:

> Hello,
>
> As you can see in my above video, Its working fine and it takes less
> than 60 seconds to save.So, Would please elaborate more on this issue?
>
> Thanks & waiting for your answer.
>
> ** Attachment added: "contact.ogv"
>
> https://bugs.launchpad.net/openobject-server/+bug/1233153/+attachment/3853260/+files/contact.ogv
>
> ** Changed in: openobject-server
> Status: New => Incomplete
>
> --
> You received this bug notification because you are a member of OpenERP
> Drivers, which is subscribed to OpenERP Server.
> https://bugs.launchpad.net/bugs/1233153
>
> Title:
> Save partner information gets very slow
>
> Status in OpenERP Server:
> Incomplete
>
> Bug description:
> Version 7.x [bzr] / postgres 9.1 / debian linux
>
> Database has roughly 13.000 partner records.
>
> When editting a partner and modifying one of the contact records of it
> the save operation is very slow (> 60 secs sometimes). When editting
> the partner contact record directly the performance is normal.(< 1
> sec)
>
> I'm at a loss what could cause this, the only thing which is odd is
> that the whole operation seems to play out in 'slow motion' in the
> log. The query log (--log-sql) shows the queries in a slower rate than
> other operations on the same installation.
>
> The save operation completes successfully eventually, even if the
> client has timed out (which is our proxy configuration)
>
> Things checked:
> - all browsers affected
> - there are no slow queries logged (>200ms) by Postgres
> - the load of the application server nor the database server increases
> noticeably
> - moved the whole installation to a local machine (to take out possible
> network errors) -> no difference
> - full vacuum of database makes no difference
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/openobject-server/+bug/1233153/+subscriptions
>