[Libreoffice-bugs] [Bug 125619] 'performance problem with plenty comments' still in 6.3 alpha1, *only after save of file/autosave*

[bugzilla-daemon at bugs.documentfoundation.org]

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

--- Comment #9 from b. <newbie-02 at gmx.de> ---
Created attachment 155628
  --> https://bugs.documentfoundation.org/attachment.cgi?id=155628&action=edit
file 'content.xml' from att. 154800 opened in firefox

... continued: 

the files manifest.xml and others opened in text-editor (gedit?) and showed
some info too cryptical for me, the file content.xml shot gedit into digital
nirvana with endless massive cpu-load and fan noise. So I thought this file was
broken, but I managed to open it with firefox. 

It consists of a header with several style definitions, and then the block I
marked blue in the screenshot repeats the same thing several thousand times,
with two variables 'svg:x' (from 80.99 to 6672,98 in steps of 64: 104 entries)
and 'svg:y' (from 0 to 1267.2 in steps of about 12.8: 100 entries). 

(I assume that represents 104 columns from A to AZ and 100 rows from 1 to 100,
with only graphical coordinates where to place something.)

I have massive difficulties imagining any program that could work effectively
with this data structure. 

The data is a !list! that can only be accessed by searching? And whose values
can only be assigned to a cell with float calculations of graphical
coordinates? 

if you do this for the full list on every dot of a move of the mouse ... you
get massive unproductive overhead. 

One might do things like this if to handle a manageable amount of values ...
but as the number of comments in calc is limited only by the number of cells in
the sheet?, this structure causes a behavior that when programming and testing
with few comments everything slides wonderfully, with larger amounts of
comments massive problems have to occur. 

(high-res screens may contribute to the impact by increasing the number of
moves that must be evaluated.)

In my opinion, one would have to rework the data structure in such a way that:
- each entry for a comment is marked as to which cell it belongs
- these 'cell coordinates' can be used as an index to access the comments,
(a two-dimensional array ([0 to max-used-col; 0 to max-used-row]: string;
attributes)?

But that's a job for programmers, my contribution as a user is to show that the
data structure used is something between ridiculous and terrible.

Please correct me and I apologize very much, of course, if I misunderstood
something.

reg. 

b.

-- 
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/20191108/41e1ec81/attachment.html>