Bug #3504: WCartesianChart Firefox V29/V30 CPU usage problem when using PointSeries with more than 500 entries - Wt - Redmine

Actions

Copy link

Bug #3504

closed

WCartesianChart Firefox V29/V30 CPU usage problem when using PointSeries with more than 500 entries

Added by Stefan Ruppert over 10 years ago. Updated about 10 years ago.

Status:

Closed

Priority:

High

Assignee:

Koen Deforche

Target version:

3.3.4

Start date:

07/23/2014

Due date:

% Done:

Estimated time:

Description

Hi,

when using PointSeries with some thausands of entries Firefox V29/V30 (under linux) slows down and for about 1-5 seconds is at 100% CPU usage. Within this time firefox does not react on any input mouse/keyboard, even the menu bar does not work.

Attached you will find a TestApp which creates a WCartesianChart with around 6000 entries. Using this chart with LineSeries the response time of Firefox is ok!

With Google Chrome PointSeries has also a good response time!

I have implemented a zoom function by using the mouse wheel of the chart will easily show the problem!

Regards,

Stefan

Files

TestGraphApp.cc (10.3 KB) TestGraphApp.cc

Test WtApp showing the WCartesianChart Problem with Firefox (under Linux)

Stefan Ruppert, 07/23/2014 05:56 PM

Actions

Copy link

Updated by Koen Deforche over 10 years ago

Status changed from New to Feedback
Assignee set to Koen Deforche

Hey,

I believe it is a bug specific for Firefox/Linux. Firefox/Windows and Firefox/Mac (same versions) do not suffer from this problem. The only workaround I could find is to remove shadow.

Regards,

koen

Actions

Copy link

Updated by Stefan Ruppert over 10 years ago

Hi Koen,

thanks for investigating this problem. For now I'll disable the shadow effect for point series.

What about a general zoom functionality as implemented in the TestGraph? The only thing which is missing from my point of view is calculating automatically new Y-Axis range based on the new X-Axis range. I didn't find/understand the auto range calculation in the current implementation...

Regards,

Stefan

Actions

Copy link

Updated by Koen Deforche over 10 years ago

Hey,

By default the Y axis range will be automatically adjusted to the data that is available. So if you adjust the X axis range, the Y axis range will be recomputed.

I suppose then that's not what you're seeing or want?

Regards,

koen

Actions

Copy link

Updated by Stefan Ruppert over 10 years ago

Hi,

ok, then its a bug ;-/ If I set a new X range using WCartesianChart::axis(XAxis).setRange(min, max), the Y axis min/max is not changed. You can verify this, be zooming into the green values on the right side using the mouse wheel of the test app!

Regards,

Stefan

Actions

Copy link

Updated by Stefan Ruppert over 10 years ago

Hi,

Stefan Ruppert wrote:

Hi Koen,

thanks for investigating this problem. For now I'll disable the shadow effect for point series.

yesterday I played a little bit more with this problem and it is not so easy. Even if I disable the shadow firefox slows down dramatically. Also BarSeries seems to have this issue... Do you have a channel to mozilla to address such problems?

Regards,

Stefan

Actions

Copy link