Sandra McLeod
Top achievements
Rank 1
Rank 1
Sandra McLeod
asked on 02 Aug 2010, 10:04 PM
We're experiencing a significant increase in the CPU usage of our website when we upgrade from the 2090.3 version of the Telerik controls to the latest 2010.2 release. Using a performance analysis tool (JetBrains' DotTrace) we were able to compare performance with these two versions of the Telerik controls and identified that the increase in CPU time is occuring down in the guts of the RadGrid control's DataBind method.
Has anyone else experienced a similar behavior on their websites? Has there been a change in the default behavior for the Ajax RadGrid control in this latest release? It looks like the great majority of the CPU increase is coming from the following function call:
DataBind ->...->get_ResolvedDataSource->PrepareDataSource->get_FilterExpression->GetString()
We aren't configuring any type of explicit Filtering on our RadGrid controls. In our code we are binding to a DataSet, with most of the data in the dataset being string values. There haven't been any other changes to our code.. We are able to reproduce the problem simply by swapping out the referenced version of the Telerik controls.
Is this a bug in the Telerik controls? Any ideas what might have changed between these releases that would account for this change in performance?
Any help would be greatly appreciated!!
Has anyone else experienced a similar behavior on their websites? Has there been a change in the default behavior for the Ajax RadGrid control in this latest release? It looks like the great majority of the CPU increase is coming from the following function call:
DataBind ->...->get_ResolvedDataSource->PrepareDataSource->get_FilterExpression->GetString()
We aren't configuring any type of explicit Filtering on our RadGrid controls. In our code we are binding to a DataSet, with most of the data in the dataset being string values. There haven't been any other changes to our code.. We are able to reproduce the problem simply by swapping out the referenced version of the Telerik controls.
Is this a bug in the Telerik controls? Any ideas what might have changed between these releases that would account for this change in performance?
Any help would be greatly appreciated!!
4 Answers, 1 is accepted
0
Hi Sandra,
Since the Q2 release we've made some improvements which might resolve the performance issues with RadGrid you are seeing. Please try the latest internal build and let us know if you are still observing the problems with it.
Best wishes,
Pavel
the Telerik team
Since the Q2 release we've made some improvements which might resolve the performance issues with RadGrid you are seeing. Please try the latest internal build and let us know if you are still observing the problems with it.
Best wishes,
Pavel
the Telerik team
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 Public Issue Tracking
system and vote to affect the priority of the items
0
Sandra McLeod
Top achievements
Rank 1
Rank 1
answered on 03 Aug 2010, 01:27 PM
Thanks, Pavel. The new "internal" release resolves this problem with the Q2 release. The performance is now consistent with what it had been for previous releases of your product.
Can/should we upgrade our production websites to this new internal release? Is it truly "production ready"?
-Sandra
Can/should we upgrade our production websites to this new internal release? Is it truly "production ready"?
-Sandra
0
Hello Sandra,
Since internal builds are uploaded twice per week, they are generally not well tested and are not intended for use in production. In this case we have performed load testing with the Grid and a few other controls to ensure that the performance is at a level comparable to that of the Q1 release. Otherwise no extensive testing has been performed. This applies to all controls.
A service pack is scheduled for release in the second half of August (around three weeks from now). I think the safest option for you is to revert to the Q1 SP2 release and wait until the next service pack. Please excuse us for the caused inconvenience and let us know if we can assist you further.
Kind regards,
Pavel
the Telerik team
Since internal builds are uploaded twice per week, they are generally not well tested and are not intended for use in production. In this case we have performed load testing with the Grid and a few other controls to ensure that the performance is at a level comparable to that of the Q1 release. Otherwise no extensive testing has been performed. This applies to all controls.
A service pack is scheduled for release in the second half of August (around three weeks from now). I think the safest option for you is to revert to the Q1 SP2 release and wait until the next service pack. Please excuse us for the caused inconvenience and let us know if we can assist you further.
Kind regards,
Pavel
the Telerik team
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 Public Issue Tracking
system and vote to affect the priority of the items
0
Sandra McLeod
Top achievements
Rank 1
Rank 1
answered on 03 Aug 2010, 02:13 PM
Thanks for letting us know. We probably can't wait until August since this is impacting our customers, so we'll need to revert to an older version for now.
We can't use the Q1 release since it had a bug that the Q2 release had fixed that caused problems for our customers who are still using IE6. But, we had good success with the 2009 Q3 release so we'll probably just revert to that version for now.
Thanks very much for your help,
-Sandra
We can't use the Q1 release since it had a bug that the Q2 release had fixed that caused problems for our customers who are still using IE6. But, we had good success with the 2009 Q3 release so we'll probably just revert to that version for now.
Thanks very much for your help,
-Sandra