Apache OpenOffice (AOO) Bugzilla – Issue 81525
Poor performance converting text to table of very larga amount of data
Last modified: 2013-08-07 14:38:26 UTC
Ooo writer has poor performance when it try to convert a large volume of data to table. All data has separate of space charset. I select all data "Ctrl + a" Select a option "Table" in menu bar > Convert > Text to Table. Obs: In "convert text to table" windows i inform to OOo writer the column is separate of space charset. In Ooo writer processing for 15 minutes in my computer and it can not to convert (Ooo_bug.png). In Microsoft Word successful convert in only 3 or 4 minute (MS_Word.png). My computer is a Intel Pentium IV 2.80 Mhz with 512 RAM running windows XP SP2.
Created attachment 48197 [details] ScreenShot of MS Word successful convert text to table
Created attachment 48198 [details] OOo writer can not convert text to table
Created attachment 48199 [details] Archive to reproduce Ooo poor convert peformance
Created attachment 48200 [details] Archive to reproduce Ooo poor convert peformance
Tested on two machines: 1. Athlon64 2800, 1Gb RAM, WinXP SP2: - OOo 2.2.1 - 4 min + crash when start scrolling - MS Word 2007 - <2 min 2. Athlon64 3700, 2Gb RAM, WinXP SP2: - OOo 2.2.1 - <3 min - MS Word 2007 - <2 min
Canis; You can test it in a more modest computer ? I tested in AMD Athon XP 1700+, and Ooo writer has poor performance
Can confirm with OOo 2.3 RC(1-2?) AMD Athlon 1 GHz, 1.2 GB RAM Win2k SP4 Real-Life Workload After > 12 min NO reaction from OOo Writer. Will let it an additional 10 minutes, to see IF anything happens. But chances look grim for a success.
Well, after well over 30 minutes, NO reaction from OOo 2.3 RC1(or 2?). I therefore killed the process.
I tested with OOo writer 2.3 Release Candidate 3 (build OOG680_m5). I've the same poor performance.
MRU->AMA: converting large amounts of data like in the attached txt takes about 3 or 4 times longer than in another product. When I tried with OO 2.3, it took about 15 min to finish. Please have a look, if this could be optimized anyway. Thanks.