openerp-india team mailing list archive

["Kyle Waid - http://www.gcotech.com" <1044054@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

6.1 OpenERP implemented transaction isolation, and an abusive locking
policy. In a production system with many concurrent users accessing the
system 20-30 + if most actions are performed on table res_users it will
lock out the system until its transaction is finished.

We have experienced issues, where the system frequently becomes
unusable. A case scenario would be  a user altering a purchase price of
a product, it updates uid, and date. It hangs on this query for several
minutes. The result is that the user sees the gears spinning for several
minutes. It is not a performance issue, but an abusive locking policy.

Another issue, we were not able to create new user groups. This is
because it seemed the table was locked, this caused a transaction wait.
Other transactions became locked, waiting for the group query to create.
It results in a cascading lock, meaning that no user can use the system
effectively disabling the system.

This is a regression from 6.0, that did not suffer from such an issue.
An example from postgres showing the shared lock, and queries that were
being blocked in a cascaded fashion

** Affects: openobject-addons
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of OpenERP
Indian Team, which is subscribed to OpenERP Addons.
https://bugs.launchpad.net/bugs/1044054

Title:
  [6.1] abusive locking policy res_users

Status in OpenERP Addons (modules):
  New

Bug description:
  6.1 OpenERP implemented transaction isolation, and an abusive locking
  policy. In a production system with many concurrent users accessing
  the system 20-30 + if most actions are performed on table res_users it
  will lock out the system until its transaction is finished.

  We have experienced issues, where the system frequently becomes
  unusable. A case scenario would be  a user altering a purchase price
  of a product, it updates uid, and date. It hangs on this query for
  several minutes. The result is that the user sees the gears spinning
  for several minutes. It is not a performance issue, but an abusive
  locking policy.

  Another issue, we were not able to create new user groups. This is
  because it seemed the table was locked, this caused a transaction
  wait. Other transactions became locked, waiting for the group query to
  create. It results in a cascading lock, meaning that no user can use
  the system effectively disabling the system.

  This is a regression from 6.0, that did not suffer from such an issue.
  An example from postgres showing the shared lock, and queries that
  were being blocked in a cascaded fashion

To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-addons/+bug/1044054/+subscriptions