View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0000265SOGoBackend Generalpublic2009-11-27 15:362010-04-02 20:26
ReporterwsourdeauAssigned To 
PrioritynormalSeverityminorReproducibilityhave not tried
Status newResolutionopen 
Summary0000265: user defaults: possible optimization
Description

Multiple inovcations of "synchronize" can be attempted during the same requests, triggering multiple updates for the same database row.

It would be faster to keep the changed data in memory until the end of the request and flush the content only then with some kind of "commit" mechanism.

See dispatchRequest: in SOGo.m

TagsNo tags attached.

Activities

ludovic

ludovic

2010-03-19 17:55

administrator   ~0000760

We need to find a way to efficiently benchmark this with a few hundreds fake users to make sure it has a real impact on performance.
wsourdeau

wsourdeau

2010-04-02 20:26

viewer   ~0000864

Not important for now. When saving preferences, the user row is only updated once, because "synchronize" is only invoke once. Therefore this situation happens in rare cases.

Issue History

Date Modified Username Field Change
2009-11-27 15:36 wsourdeau New Issue
2010-03-17 20:02 ludovic Target Version => 1.2.2
2010-03-19 17:55 ludovic Note Added: 0000760
2010-04-02 20:26 wsourdeau Note Added: 0000864
2010-04-02 20:26 wsourdeau Target Version 1.2.2 =>