[Libreoffice-bugs] [Bug 76324] CALC becomes very slow with 5000+ comments

[bugzilla-daemon at bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=76324

a07cd040897db54e103c at spambog.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |---

--- Comment #66 from a07cd040897db54e103c at spambog.com ---
For me the bug is not resolved at all. Only the Linux version seems to be
fixed. In Windows only slight improvements were noticable. The main problem
seems to be already present. See below.

@Buovjaga: this is *not* a "new issue", so reopened.

Tested with Debian buster x64:

Version: 6.1.3.2
Build-ID: 1:6.1.3-2
CPU-Threads: 2; BS: Linux 4.18; UI-Render: Standard; VCL: x11; 
Gebietsschema: de-DE (de_DE.UTF-8); Calc: group threaded

Result:
- loading/saving copying/pasting of/in "calc document with many comments (~8k)"
is substantially faster, so i would not longer consider it to be a problem
- loading/saving copying/pasting of/in "calc document with many comments (~8k)"
is still slower than it would be with "normal" cell contents instead of
comments
- no crashes
- no huge memory useage
- file saved successfully
- file saved in fair time

Tested with Windows Server 2008 R2 x64:

Version: 6.0.6.2 (x64)
Build-ID: 0c292870b25a325b5ed35f6b45599d2ea4458e77
CPU-Threads: 16; BS: Windows 6.1; UI-Render: Standard; 
Gebietsschema: de-DE (de_DE); Calc: group

Result:
- loading: 35s
- copying columns A+B: 85s
- pasting copied columns to C+D: 50s, mem useage grew to 280 MB
- saving: 90s, mem useage grew to 1.200 MB
- closing! calc: 150s (!)

During all the steps above, only one (of 16) cpu cores was used with a load of
100%.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice-bugs/attachments/20181221/49678d3d/attachment.html>