Issue 97722

Summary: performance: rendering of big line charts is to slow in inplace edit mode
Product: General Reporter: Rainer Bielefeld <rainerbielefeld_ooo_qa>
Component: chartAssignee: kla <thomas.klarhoefer>
Status: CLOSED IRREPRODUCIBLE QA Contact: issues@graphics <issues>
Severity: Trivial    
Priority: P3 CC: IngridvdM, issues
Version: 3.3.0 or older (OOo)Keywords: performance
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Issue Type: ENHANCEMENT Latest Confirmation in: ---
Developer Difficulty: ---
Issue Depends on: 97724, 97749    
Issue Blocks:    
Attachments:
Description Flags
Sample file
none
Sample file none

Description Rainer Bielefeld 2009-01-03 12:33:45 UTC
With "Ooo 3.0.0 (DE) Multilingual version German UI WIN XP: [OOO300m9
(Build9358)]" and "Ooo 3.1 Multilingual version German UI WIN XP: [DEV300m36
(Build 9369)]" I have serious performance problems using line charts with big
data sources.
The testfiles I provide are data collections from a PLC, what stores 24 data
points (temperatures ...) every 12 minutes in 3 data blocks.

Structure of the sample files:
sheets "db4000 ... DB4002" contain original data from the PLC
sheets "Daten1 ... Daten3" contain data with correct formating
sheets "Auswertung1 ... Auswertug3" contain data combinations for use in charts
(Auswertung2 not used) and for additional comparison.
sheets "Diagrammxxxx" contain diagrams (Diagramm2 not used)

"Problems.ods" contains 1600 measurements and still is (more or less) usable
"Bigproblems" contains 4035 measurements, chars are unusable.
I zipped both testfiles, pls. unzip before your tests.

My PC:
Graphic Card: Nvidia GeForce 7300 LE
Processor: AMD Athlon 64 Bit 3500+
Monitor : 1024*768

I will open further issues with other performance problems related to this one.

Here my first problem: Modifying sub heading takes very much time
Steps to reproduce:

0. open WIN Task Manager so that you can see processor load
1. Open "Problems.ods" with sheet "Diagramm1"
2. doubleclick white chart area below legend to open "chart mode"
3. Use scroll slider to make heading visible
   expected: that should be possible within a second
   actual: it will take several minutes to reach heading
11. No open "Bigproblems.ods" with sheet "Diagramm1" and redo from "2."  
    - hope you have no other plans for the weekend ;-)
Comment 1 Rainer Bielefeld 2009-01-03 12:39:58 UTC
Created attachment 59111 [details]
Sample file
Comment 2 Rainer Bielefeld 2009-01-03 12:43:27 UTC
Created attachment 59112 [details]
Sample file
Comment 3 Rainer Bielefeld 2009-01-04 15:26:12 UTC
I believe it's a redraw problem
Comment 4 kla 2009-01-06 09:08:50 UTC
@IHA: It's an really big chart but the performance should be (as Rainer has
written) a "little bit optimized".
@Rainer: thx for your support.
Comment 5 IngridvdM 2009-05-19 16:11:17 UTC
@aw, users find that scrolling a sheet while chart is in edit mode is to slow.
This must be caused by the rendering routines as the chart-view/draw-model is
not changed during scrolling. Please have a look whether you can enhance the
speed of the rendering routines. Thanks a lot in advance!
Some further information: The repeated CompleteRedraw-calls do not consume less
time than the first paint call.
Comment 6 Armin Le Grand 2009-07-28 15:00:42 UTC
AW: Need to wait for #i101491# (cws aw074) being integrated; before this (where
exactly such problems were already addressed) the results will not be good.
Removing from CWS aw075 again.
Comment 7 Armin Le Grand 2009-08-05 16:36:04 UTC
AW->rainerbielefeld: Please take a look at DEV300 m54 and check if this fulfils
Your needs.
Comment 8 Rainer Bielefeld 2009-08-06 05:39:01 UTC
I checked with "Ooo Dev 3.2.0 multilingual version English UI WIN XP: [DEV300m53
(Build 9412)]", "Ooo 3.1.0 WIN XP multilingual version German UI activated 
[OOO310m11 (Build 9399)]", "2.4.1  Multilingual version German UI WIN XP:
[680m17(Build9310)]".

I opened "Bigproblems.ods", did reported steps 0 ...3, doubleclicked subheading,
placed caret in subheading and then I pulled horizontal scroll slider to left or
right end. In all 3 versions it took app. 7 seconds until view on the chart
reaches final position matching with current new scroll slider position.
Unfortunately I do not have 3.0 any longer available, but I remember that it
took much longer (several minutes) with that version. I hope I will find the
time during weekend to compare with 3.0

So my resume: It's still rather slow, and there is no significant performance
difference between 2.4, 3.1, 3.2. It seems that the problems that came up with
3.0 and made OOo unusable for those charts has been solved in 3.1
Comment 9 thorsten.ziehm 2009-11-04 13:50:00 UTC
When this issue is solved, please close it as resolution/fixed. If it isn't
fixed, please change the target of this issue. OOo 3.2 is in stopper stage and
this issues isn't a stopper in my view.
Comment 10 kla 2009-11-10 13:31:45 UTC
@Rainer: I've change the target. Please check, if this issue is solved. If so,
please close it as resolution/fixed.
Comment 11 Rainer Bielefeld 2010-01-25 08:50:51 UTC
I did a test due to "comments from kla Tue Nov 10 13:31:45 +0000 2009", but
unfortunately I forgot to post the result: Speed has become much better.

But in between, we have a terrible regression, please see Issue 108636!
Comment 12 kla 2010-11-24 10:03:50 UTC
reassign to kla
Comment 13 kla 2010-11-24 10:04:54 UTC
workforme
Comment 14 kla 2010-11-24 10:05:19 UTC
HI, as you has written, the speed has become much better i close this issue.
Issue 108636 will handled seperately.