View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0000265||SOGo||Backend General||public||2009-11-27 15:36||2010-04-02 20:26|
|Priority||normal||Severity||minor||Reproducibility||have not tried|
|Summary||0000265: user defaults: possible optimization|
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
|Tags||No tags attached.|
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.
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.