Issue 118224 - dispose none linear timing in mail merge regarding the number of processed database elements
Summary: dispose none linear timing in mail merge regarding the number of processed da...
Status: CONFIRMED
Alias: None
Product: Writer
Classification: Application
Component: ui (show other issues)
Version: OOo 3.2.1
Hardware: All All
: P3 Normal (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-28 08:31 UTC by clutz
Modified: 2013-02-07 22:37 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
performance-test of mail merge jobs in OOo (38.70 KB, application/pdf)
2011-06-28 08:31 UTC, clutz
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description clutz 2011-06-28 08:31:25 UTC
Created attachment 76649 [details]
performance-test of mail merge jobs in OOo

Regarding to my performance-Tests for issue #118222 (the corresponding diagram is also attached to this issue) it is obvious to see that mail merge into one file in OOo has a non linear timing behaviour regarding the number of processed database elements (n). It seems that the OOo mail merge has a complexity of O(nĀ²).

Due to this behaviour the mail merge of large jobs into one file is in much scenarious not practical. On my host the merge with over 500 datasets needs more than acceptable time. We have got real scenarios where people need to perform mail merge jobs with over 4000 datasets.

The improvement should be to get a nearly linear timing behaviour by optimizing the current mail merge algorithms and underlying data structures.
Comment 1 clutz 2011-09-06 20:58:51 UTC
there is a patch available for this in LibO:

http://cgit.freedesktop.org/libreoffice/core/commit/?id=e024f616934bb78fba8c8101264806d507068d7e
Comment 2 Oliver-Rainer Wittmann 2012-06-13 12:32:21 UTC
getting rid of value "enhancement" for field "severity".
For enhancement the field "issue type" shall be used.