openerp-india team mailing list archive
-
openerp-india team
-
Mailing list archive
-
Message #24999
[Bug 1219881] Re: Performance improvement on bank statement validation
I think many performance problems are based on o2m inserts/updates
(create/write)
a create/write off a line causes function fields in the "one" record to
be recalculated multiple times
example
moves = []
for line in cr.dictfetchall():
line['name'] = 'neutral-'+ move['date'],
#self.create_move(cr, uid, line, vals, context ) #<---- very time consuming
moves.append(self.create_move(cr, uid, line, vals, context ))
move_obj.write(cr, uid, [move_id], {'line_id': moves}, c ) #<-- much faster
may be other approaches are better
--
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/1219881
Title:
Performance improvement on bank statement validation
Status in OpenERP Addons (modules):
New
Bug description:
Hello,
Our customer need to validate bank statement with 15'000 lignes on
average . Today they slice the bank statement into 1000 lignes and,
even though, It takes hours to validate it.
Same probleme to cancel a bank statement.
This point becomes more and more critical for us especially in
e-commerce business.
Can you propose improvement please ?
Frederic Clementi
Camptocamp
To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-addons/+bug/1219881/+subscriptions
References