This is a migrated thread and some comments may be shown as answers.

Major performance decrease in 2015 Q1

5 Answers 64 Views

Gauge

This is a migrated thread and some comments may be shown as answers.

Andreas asked on 09 Jun 2015, 12:43 PM

Hi,

We use the RadGauge a lot, but lately we had some real performance issues, mostly on tablets (iPad)!

When reverting back to a telerik version prior to 2015 Q1 (2014 something), all issues are gone...

In a simple example:

<%@ Page Language="vb" AutoEventWireup="false" CodeBehind="gauge.aspx.vb" Inherits="TestaTredjepartWeb.gauge" %>

<!DOCTYPE html>

<html xmlns="http://www.w3.org/1999/xhtml">

<head runat="server">

<title></title>

</head>

<body>

<form id="form1" runat="server">

<script type="text/javascript">

window.__dt = new Date();

setTimeout(function () { alert((new Date()) - window.__dt - 10); }, 10);

</script>

<asp:ScriptManager ID="s" runat="server">

</asp:ScriptManager>

<div>

<asp:Button ID="btn" runat="server" />

<telerik:RadRadialGauge ID="rrg" runat="server" Transitions="false">

<Pointer Value="44" Color="Red" Cap-Color="Yellow"></Pointer>

<Scale>

<Labels Position="Outside" Color="Gray" Font="normal 10px Segoe UI, Tahoma, Helvetica" />

<Ranges>

<telerik:GaugeRange From="0" To="40" Color="Red" />

<telerik:GaugeRange From="40" To="90" Color="Yellow" />

<telerik:GaugeRange From="90" To="200" Color="Green" />

</Ranges>

</Scale>

</telerik:RadRadialGauge>

</div>

</form>

</body>

</html>

When running this sample on a desktop computer, the alert says about 30ms with 2014 version and 100ms with any 2015 version, on an iPad it says 150ms with 2014 version and 600ms with any 2015 version.

About 3-4 times slower!

On some pages we have multiple gauges, which makes it even worse...
The 2015 Q2 Beta is also slow...

Regards
Andreas

5 Answers, 1 is accepted

answered on 16 Jun 2015, 12:24 PM

Hello Andreas,

We have made a further investigation on the matter and this is actually a separate issue - the fix for the previous issue doesn't help. That being said I have reported this issue to our development team and logged a new public item here (http://feedback.telerik.com/Project/108/Feedback/Details/161466), so that you can monitor its status and put your comments below.

Unfortunately I cannot offer a reliable solution because the issue requires additional research, as it is more complex and providing a workaround would mean fixing the issue itself.

I have also updated your Telerik points for reporting this issue to us.

Regards,
Danail Vasilev
Telerik

Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items