Issue 109276 - Calc is extremely slow when spreadsheet has many notes (comments)
Summary: Calc is extremely slow when spreadsheet has many notes (comments)
Alias: None
Product: Calc
Classification: Application
Component: editing (show other issues)
Version: OOo 3.2 RC5
Hardware: PC Windows XP
: P3 Trivial with 5 votes (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Keywords: oooqa
: 127715 128121 (view as issue list)
Depends on:
Blocks: 102716 111037 111390
  Show dependency tree
Reported: 2010-02-15 09:20 UTC by cianoz
Modified: 2019-09-10 07:35 UTC (History)
7 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: 4.1.6
Developer Difficulty: ---

Calc spreadsheet with many notes that slow down operations (578.69 KB, application/vnd.oasis.opendocument.spreadsheet)
2010-02-15 09:21 UTC, cianoz
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description cianoz 2010-02-15 09:20:13 UTC
If you have a large spreadsheet with a great number of comments ("notes") every
operation that involves moving or copying the notes will dramatically slow down
the program. The greater the number of comments the longer OO takes to perform

For example open the attached spreadsheet, that have a lot of comments inserted,
and try to apply a filter on any column. It takes a very long time to apply the

Another example on the same file, but even more heavy: select the entire sheet
content then cut and paste in place. OO Calc will freeze and you have to
terminate it (maybe it will paste the content sooner or later but i tried to
wait for minutes)

Select the entire sheet then remove/delete all notes and try any of the previous
operations: filter is applied in a second and cut and paste takes only a few

This is quite a serious problem for those (like us) that use big spreadsheets in
a business environment, where filters are used as an habitual tool for daily work.
Hope this will be fixed in the next 3.2.1
Comment 1 cianoz 2010-02-15 09:21:29 UTC
Created attachment 67824 [details]
Calc spreadsheet with many notes that slow down operations
Comment 2 camillem 2010-05-05 17:37:53 UTC
Looks like a duplicate of issue 102716
Comment 3 daniel.rentz 2010-05-05 19:39:44 UTC
Taking this issue. See issue 111390 for an explanation. Will keep this issue
open to not forget to test the attached document after fixing.
Comment 4 Rainer Bielefeld 2010-05-10 16:50:31 UTC
I doubt that only WIN XP is affected, Issue 111037 has been reported for LINUX
Comment 5 niklas.nebel 2010-05-10 17:05:51 UTC
Reassigning to dr - "started" with owner "spreadsheet" doesn't make much sense.
Comment 6 niklas.nebel 2010-05-10 17:06:52 UTC
restore "started" state
Comment 7 orcmid 2016-02-09 22:29:26 UTC
Removing Accepted state since this goes back to OO.o 3.2 and appears to be in limbo.
Comment 8 orcmid 2016-02-09 22:30:32 UTC
completed the transition back to Uncomfirmed.

This needs to be re-examined, and the condition characterized better.  

(I am not doubting that this might be a problem.  We just have to take a fresh look.)
Comment 9 oooforum (fr) 2019-06-03 07:28:53 UTC
*** Issue 128121 has been marked as a duplicate of this issue. ***
Comment 10 b. 2019-06-03 21:02:06 UTC
retested this bug today with AOO416m1(Build:9790)  -  Rev. 1844436
2018-10-23 12:57 under win7 pro (x64) SP1, still an issue, pls. see add. comments in #128121, could somebody pls. recheck and set to confirmed, or new?
Comment 11 Keith N. McKenna 2019-06-04 00:56:21 UTC
*** Issue 128121 has been marked as a duplicate of this issue. ***
Comment 12 b. 2019-06-04 05:49:28 UTC
hello @all, 

sorry for writing long, it is an old problem, in my opinion it is wrongly neglected, and it has - partly unnoticed / partly not attributed to the cause - considerable negative influence, i'd ask persons interested in the performance of calc to try to read to the end. 

(this info was originally written for #128121, as that is closed again as duplicate i provide an enhanced version here)

(Sorry, I'm digressing, one general problem with the handling of bugs and some ideas for improvements (admins might push to a separate thread): 

i get a 'feeling' that the handling of bugs is somewhat 'suboptimal', old bugs tend to become 'old' and 'long', and collect some 'false positive' and 'no repro' comments, thus straying the focus of the readers, new bugs become closed as duplicates, users ignore old bugs because they should be resolved, new reports are pushed away from their attention as 'resolved - duplicate', the QA team has more and more work to just manage the bugs bureaucratically ... not an optimized process. 

1. sort the comments list bottom up, newest comments on top of the list, thus focussing the attention of the reader to fresh info while he can still recheck all old info in the list below, 
2. implement some sort of 'quality commenting' for the comments (in bugzilla), there is! some good info buried under plenty of questions and useless stuff, it should be pulled to attention somehow, 
3. also sort the 'closing as duplicate' the other way around, fresh reports should be held open (they provide fresh information about the actual situation) while old reports can be closed, the info is still available, 
4. do 3. at least when the discussion in the old thread entered an 'unproductive state')

back to the topic: 

AOO and LO bear a long history of issues / bugs / comments / complaints regarding poor performance when using too many notes / comments in a sheet or file. 
see below list of 6 issues and retests today, still an issue, 

happy: i'm not alone, 

sad: something affecting the fun to work with OO and LO in a massive negative way is 'still in' after *10* years, 

alarming (me): work on the issue is hindered by the procedures described above under digression, 

apologize: i know this post will be 'too long' and little compatible with the 'local forms of handling' ... after ten years without significant progress and plenty attempts - of others - to handle the issue with short comments in accordance with the 'rules' ... i feel free to try another way ... it may fail, but that would not be a step backwards behind the lack of progress so far, and simply continue like yet would - probably - not bring any progress either, 

ecological: just an assumption: 8 billion people worldwide, 4 billions awake, 1 billion using computers, 10% (100 millions) using spreadsheets, 20% (20 millions) LO or OO (maybe the bug is in e$x$cel as well), 50% (10 millions) using comments, theese wasting 20 watt of cpu-power for comments ... the impact in wasted energy is about 200 Megawatt!, about one sixth of an usual big nuclear power plant :-(, with german average prices 60.000 EUR per hour? (since ten years?) 

!!! ... besides massive wasting time of users ... !!!

!!! ... and straying big frustration on those affected by the problem but without skills and time to analyze ... !!! 

satirized: wasting 2 seconds on every click of a normal user with 10000 clicks per day (~20 per minute) will waste seconds of mankind lifetime per day, thats every 6 month the impact of '911'! (ok, the time wasted on security checks at airports is somewhat 'more effective')

brutality: what i *absolutely dislike* abut that bug (deepl'ed): it creeps in unnoticed, gradually increases with the amount of data until users notice a problem, but then there's no clue what the cause is, they're wasting time on research, or slow work, or switch to another program. And even before using comments, there was no hint: 'Beware!, too many comments can drastically slow down your system!'.

history: i had a big issue with e$x$cel in the past, it killed a company, a partnership, the work of 6 years ... the symptoms had been the same, increasing slowness with no unterstandable reason ... may be it was the same issue ... ???

history 2: Honour to whom honour is due: Issue #102716 - Calc is very slow for some operations (with many notes), should be held as the original report, this one is just another duplicate, 

festivity: #102716 is reported '2009-06-12 13:20 UTC by sukender', we can hold 10th anniversary wednesday next week, prepare yourselves for a [big celebration / great memorial service], 

technical: despite that the handling of a comment shouldn't be much more complex than the handling of a cell (added positon on the screen, substracted formulae, calculation and referencing) it obviously is! in current implementations. there is some useful technical info in: 

strategy: whilest not able to solve the problem i'd suggest: 
- !!!some sort of warning to the users in orer to prevent more and more of them stepping into this trap!!!, 
- some workaround as suggested somewhere 'implement a switch to use flat comments instead of the performance killing prettyfied M$ overhead' or similar,  
- a somewhat 'deeper' information why the 'current implementation' is neccessarily ressource wasting, loops? recursions? one-way-references? search instead of indexed access? how is the workflow? (did someone organize first to prepare the display of all comments and then to hide them from visibility?) how is the data structure? 
(imho: screen is painted, mouse is moved, staying in a cell: do nothing, leaving a cell: triggering repaint where the comment must no longer be shown (delete comment representation from the comment overlay?), entering a cell: check if commented, select comment, select position to show, draw box, display ... that's not much work for a modern machine.) 
- some thoughts about an analysis of the 'current implementation' and if improvements are possible, may be also M$ would be interested? 
- crowdfunding to engage a paid programmer 

strategy 2: work together with the LO community, they have the same issue, funnily in the latest dev. releases reduced to occur after the first autosave only, thus mistakenly ignored by testers and developers, but may be they are close to a solution (just left problems with the representation / search / check in autosave info)? 

activity: searched again today (yesterday) and found three the same issues: 

Issue 109276 - Calc is extremely slow when spreadsheet has many notes (comments) 
   reported *2010*-02-15 09:20 UTC by cianoz 
   status today: Status: 	UNCONFIRMED 
   tested today: hard work for system to copy content, errors like 'no space to copy here', lightning fast after stripping comments, thus: still issue, 

Issue 117348 - freeze or out of memory , when paste a lot of cells with comment. 
   reported *2011*-03-12 04:12 UTC by paz_ohhashi 
   status today: Status: 	UNCONFIRMED 
   tested today: Issue 117348: high load and delay and 'not responding' on copying the row with comments, had to kill the task, thus: still issue, 

Issue 127715 - Changes in spreadsheet with many notes (comments) extremely slow 
   reported 2018-02-26 12:26 UTC by orion 
   status today: Status: 	UNCONFIRMED 
   tested today: visible delays alredy with very small amounts of data and comments, thus: still issue, 

and even more domino-like after noticing that comments are called 'notes' as well: 

Issue 102716 - Calc is very slow for some operations (with many notes) 
   reported  *2009*-06-12 13:20 UTC by sukender 
   this is at least Status: 	CONFIRMED
   tested today: deleting a line, heavy load and 'not responding', thus: still issue, 

Issue 111390 - OOo Calc 3.0.1 and higher --> Notes bug 
   reported: *2010*-05-05 09:12 UTC by jsteenks 
   despite being confirmed in:
   status today: Status: 	CLOSED *IRREPRODUCIBLE* 
   but some useful info in:
   tested today: small sheet, few comments, first no problem, maybe i didn't get the functionality of the sheet, unfolded invisible rows and cols, added 75k cells with '1' in it commented '1', dead, sorry, finished and came back to live after ~10 minutes, 13 % of cpu-load on hovering with the mouse over the sheet, thus: still issue, 

Issue 111037 - An example of XLS/ODS file which slows down OOo 
   reported: *2010*-04-21 11:10 UTC by hiddenman 
   this is at least Status: 	CONFIRMED
   tested today: visible delays, graphics fu**ed after deleting one column, 15 times faster after strippung comments, thus: still issue, 

i'd stop listing here, my impression: there is a 'big bug', and one will easily find plenty other complaints about performance which did not get the boildown to the root 'comments' or 'notes', but which do rely on theese effects and you'll see it once you test 'em against this issue. 

so please believe me: there is an issue!, 

this bug is! a duplicate of plenty others, as they are still unresolved it's an appeal to take this issue seriously ... 

ok, thats what i could do to pull attention to this issue, hope it helps ... 


Comment 13 oooforum (fr) 2019-07-22 13:08:07 UTC
*** Issue 127715 has been marked as a duplicate of this issue. ***
Comment 14 b. 2019-09-09 18:17:35 UTC
this bug is 9,5 years old!, 

it ist very easy to reproduce, 

it has at least 2 duplicates in the bugzilla, 

and no one has taken a heart to set it to 'new'? 

no developer will care for it while 'unconfirmed', 

pleas, please, please ... somebody with the power to do so - mine isn't, just a newbie - set it to 'new', it is! a bug, and it needs attention ... 


Comment 15 Peter 2019-09-10 07:35:27 UTC
Ok I set it to confirmed.