Bug 51160 - EDITING: Update for charts with big data table takes minutes instead of seconds
Summary: EDITING: Update for charts with big data table takes minutes instead of seconds
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Chart (show other bugs)
Version:
(earliest affected)
3.5.1 release
Hardware: Other All
: medium major
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords: perf, possibleRegression
Depends on:
Blocks:
 
Reported: 2012-06-16 14:55 UTC by Jim Warren
Modified: 2015-12-15 11:16 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jim Warren 2012-06-16 14:55:14 UTC
Using LibreOffice 3.5.4.2 
Build ID: 165a79a-7059095-e13bb37-fef39a4-9503d18
on a 15" mid-2010 MacBookPro under OS X 10.6.8

Problem description: 
Just converted some files from Mac Microshaft Oriface 2004 Excel to LO Calc.
One is a 9800-row daily spreadsheet including several columns of different numeric data.
When attempting to create an entirely new graph of a 2x9800 array of date & xxx.x decimal data, it took maybe 4-8 MINUTES to struggle through every single click or character entered in the graph parameters!
Also took the same amount of time on every scheduled interim backup.
The Mac's Activity Monitor showed that, for much of that time, LO was "not responding".  However, eventually it DID respond - and completed the desired task.  Eventually.
In comparison, Excel from The Evil Empire was always quite efficient, even with these "very large" spreadsheets.
Even before trying to create this graph of "large" data, interim auto-saves and a commanded or closing save took perhaps 15 seconds.
Worse still, these humongous delays also occur even in creating or updating graphs of much smaller 2D datasets - e.g. this year by day x daily closing dollar-amount.

Steps to reproduce:
Simply changing a single datum in the array being graphed.
Or changing a single character of a single parameter of the graph (e.g., line-width).

Current behavior:
As described above.

Expected behavior:
MUCH less turgid!  NO "not responding" periods - especially not when followed, eventually, by some kind of response and [eventual] task completion.

Platform (if different from the browser): 
Not sure how the browser is related to the platform running LibreOffice.
  15" MacBook Pro, mid-2010 model (model A1286), 8GB memory,
  2.53 GHz Intel Core i5, Intel HD graphics 256MB shared SDRAM plus NVIDIA GeForce GT 330M 256GB GDDR3
Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:12.0) Gecko/20100101 Firefox/12.0
Comment 1 Rainer Bielefeld Retired 2012-06-17 00:43:30 UTC
Not a valid Bug Report

@reporter:
Thank you for your report – unfortunately important information is missing.
May be hints on <http://wiki.documentfoundation.org/BugReport> will help you to find out what information will be useful to reproduce your problem? If you believe that that  is really sophisticated please as for Help on a user mailing list
Please:
- Write a meaningful Summary describing exactly what the problem is. 
  It seems we are talking about CHARTs? If yes? I can confirm the problem.
- Attach a sample document (not only screenshot) or refer to an existing 
  sample document in an other Bug with a link.
- Attach screenshots with comments if you believe that that might explain the 
  problem better than a text comment. Best way is to insert your screenshots
  into a DRAW document and to add comments that explain what you want to show
- Contribute a document related step by step instruction containing every 
  key press and every mouse click how to reproduce your problem 
  (similar to example in Bug 43431)
– if possible contribute an instruction how to create a sample document 
  from the scratch
- add information 
  -- what EXACTLY is unexpected
  -- and WHY do you believe it's unexpected (cite Help or Documentation!)
  -- concerning your PC (video card, ...)
  -- concerning your OS (Version, Distribution, Language)
  -- concerning your LibO version (with Build ID if it's not a public release)
     and localization (UI language, Locale setting)
  –- Libo settings that might be related to your problems 
    (video hardware acceleration ...)
  -- how you launch LibO and how you opened the sample document
  –- If you can contribute an AOOo Issue that might be useful
  -- everything else crossing your mind after you read linked texts

Even if you can not provide all demanded information, every little new information might bring the breakthrough.
Comment 2 Rainer Bielefeld Retired 2012-06-26 21:57:30 UTC
No Idea what reporter's problem might be, so I hijack the bug.

Steps to reproduce:

0. Download attached sample document
1. open document from File explorer by double click with 3.5.5.1  German UI/Locale [Build-ID: c9944f7-48b7ff5-0507789-54a4c8a-8b242a8] on German WIN7 Home Premium (64bit) (or from LibO File menu)
1.1 disable 'Tools -> Cell contents -> Auto Calculate' if necessary
3. Change Cell B6 contents to 100
   > Works fine, no delay visible
4. Click Chart at the end
   >  Control points appear
5. <control+x> for cut
   Expected: chart disappears more or less without delay
   Actual: No reaction, maximum processor load, increasing memory used by 
   soffice.bin

LibO will be blocked for  approximately 5 minutes

10. click into F10 and <control+v> to insert Chart  
    Works fine
11. Try to modify Cells B2 - C2 - D2 to "1" - "0,5" - "0,25"
    Expected: possible within few seconds
    Actual: After change in B2 several Minutes blocked

[Reproducible] with Server installation of  Master "LOdev 3.6.0alpha0+  – WIN7 Home Premium (64bit) ENGLISH UI [Build ID: 475d0c5-829fc92-39746e8-206648e-fefd87]" (2012-02-14)

OOo 3.1.1 does all those jobs within few seconds.
LibO 3.3.3 does all those jobs within few seconds.
LibO 3.4.5 does all those jobs within few seconds.

With all these versions after Step 11 I can fill down the 3 new values until end of data range, Chart will show new values within few seconds

@Markus:
Please set Status to ASSIGNED and add yourself to "Assigned To" if you accept this Bug
Comment 3 Rainer Bielefeld Retired 2012-06-26 22:29:27 UTC
Already [Reproducible] with "LibreOffice 3.5.1.2 German UI/Locale [Build-ID: dc9775d-05ecbee-0851ad3-1586698-727bf66] on German WIN7 Home Premium (64bit)
Comment 4 Kohei Yoshida 2012-11-06 18:46:37 UTC
(In reply to comment #2)
> No Idea what reporter's problem might be, so I hijack the bug.
> 
> Steps to reproduce:
> 
> 0. Download attached sample document

Rainer, I don't see any document attached to this bug report.
Comment 5 Dan Dascalescu 2013-06-28 19:13:15 UTC
LibreCalc is generally visibly slower than Excel. Even the font size of the focused text takes about one second to be updated in the toolbar.

Simple charts again take 1-2 seconds to update after changing some options. So I wouldn't be surprised that LC can get a lot slower with lot of data.
Comment 6 Robinson Tryon (qubit) 2013-10-16 02:01:09 UTC
Hi Jim,

Thanks for the bug report! It's important to us to hear from users who are concerned about a slow-down that they're experiencing in LibreOffice.

As Kohei notes below, I'm not seeing any files attached to demonstrate how to reproduce your particular performance problem.

It's possible that your performance issue has already been reported or fixed. First, please grab a recent build of LibreOffice from our download site and see if Calc's speed has increased: https://www.libreoffice.org/download/

If your problem is still present, please take a look at this list of bugs in Bugzilla and see if one of them describes the slowdown you're seeing:
https://bugs.freedesktop.org/buglist.cgi?list_id=354940&status_whiteboard_type=allwordssubstr&query_format=advanced&status_whiteboard=perf&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&component=Spreadsheet&product=LibreOffice

If you can't find an existing bug in Bugzilla that matches your problem, please provide a test file and a short set of repro steps so we can hone-in on your problem quickly.

Thanks!
Comment 7 QA Administrators 2014-05-17 00:34:14 UTC
Dear Bug Submitter,

Please read the entire message before proceeding.

This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 
https://wiki.documentfoundation.org/QA/FDO/NEEDINFO

If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.


Thank you for helping us make LibreOffice even better for everyone!


Warm Regards,
QA Team
Comment 8 Jim Warren 2014-05-17 20:43:50 UTC
Importing "large"(?) datasets (e.g. 10,000x2 or 10,000x6 arrays) and their graphs from Microshaft's Excel 2004 for the Mac, and having monumentally turgid (as in many minutes!) display of the graphs on every keystroke of any attempted change seems to have been cured by (or before) LibreOffice 4.2.4.  [APPLAUSE!]

If anyone DOES still want copies of the datasets, I'll be happy to upload 'em, but won't bother unless someone request 'em.

THANKS!

--jim; Jim Warren, open-govt & tech-civlib advocate & sometime columnist
  http://en.wikipedia.org/wiki/Jim_Warren_%28computer_specialist%29
  justjim36 on twitter  |  Jim Warren on Facebook
Comment 9 QA Administrators 2014-06-01 20:30:10 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided):

a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. 
Please do not:
a) respond via email 
b) update the version field in the bug or any of the other details on the top section of FDO
Comment 10 Robinson Tryon (qubit) 2015-12-15 11:16:39 UTC
Migrating Whiteboard tags to Keywords: ( perf PossibleRegression)
[NinjaEdit]