Christopher Blickley
Top achievements
Rank 2
Christopher Blickley
asked on 08 Jan 2008, 04:46 AM
Hello,
I was taking a first look at the online demos of the classic RadGrid vs. the RadGrid Prometheus. When I compare the two on the demo website, it appears that the Prometheus version is noticeably slower than the classic version for things like sorting, and especially paging.
I obviously want to start working with the Prometheus version, but am concerned that there is a significant performance hit.
Does anyone else notice this? Perhaps it has been discussed already...
Thanks,
Chris
I was taking a first look at the online demos of the classic RadGrid vs. the RadGrid Prometheus. When I compare the two on the demo website, it appears that the Prometheus version is noticeably slower than the classic version for things like sorting, and especially paging.
I obviously want to start working with the Prometheus version, but am concerned that there is a significant performance hit.
Does anyone else notice this? Perhaps it has been discussed already...
Thanks,
Chris
13 Answers, 1 is accepted
0
Vladimir
Top achievements
Rank 1
answered on 08 Jan 2008, 06:34 PM
Chris,
Can you post the url for the example where classic RadGrid is faster than "Prometheus" RadGrid?
Vlad
Can you post the url for the example where classic RadGrid is faster than "Prometheus" RadGrid?
Vlad
0
Christopher Blickley
Top achievements
Rank 2
answered on 08 Jan 2008, 08:40 PM
Sure,
The performance delay I am seeing is only of Telerik's site....I went back and tested the two RadGrid versions on my machine using the demos that are installed and it seems pretty quick. I'm not sure why it would be slower on Telerik's site vs. my PC, but perhaps there is more overhead with Prometheus and it is taking longer to go over the wire? I'm just guessing....
Interestingly, the classic example uses full page refreshes, but is really fast. The Promotheus is using Ajax and is noticeably slower to change pages. Some page changes in the grid are quicker than others, but overall, it is noticeably slower overall.
-Chris
Prometheus:
http://www.telerik.com/demos/aspnet/prometheus/Grid/Examples/GeneralFeatures/Paging/DefaultCS.aspx
Classic:
http://www.telerik.com/demos/aspnet/Grid/Examples/GeneralFeatures/Paging/DefaultCS.aspx
The performance delay I am seeing is only of Telerik's site....I went back and tested the two RadGrid versions on my machine using the demos that are installed and it seems pretty quick. I'm not sure why it would be slower on Telerik's site vs. my PC, but perhaps there is more overhead with Prometheus and it is taking longer to go over the wire? I'm just guessing....
Interestingly, the classic example uses full page refreshes, but is really fast. The Promotheus is using Ajax and is noticeably slower to change pages. Some page changes in the grid are quicker than others, but overall, it is noticeably slower overall.
-Chris
Prometheus:
http://www.telerik.com/demos/aspnet/prometheus/Grid/Examples/GeneralFeatures/Paging/DefaultCS.aspx
Classic:
http://www.telerik.com/demos/aspnet/Grid/Examples/GeneralFeatures/Paging/DefaultCS.aspx
0
Hi Christopher,
This is really strange. I have performed some testing with the examples you referenced and the Prometheus Grid was always quite a bit faster to load. I even tested on IE6 and observed a slight drop in performance but the Prometheus version was still quicker then the Classic. Could you tell us on what browser are you viewing this?
Best wishes,
Yavor
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
This is really strange. I have performed some testing with the examples you referenced and the Prometheus Grid was always quite a bit faster to load. I even tested on IE6 and observed a slight drop in performance but the Prometheus version was still quicker then the Classic. Could you tell us on what browser are you viewing this?
Best wishes,
Yavor
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
0
Christopher Blickley
Top achievements
Rank 2
answered on 11 Jan 2008, 12:57 AM
I am using IE7. I ran the examples from home and from work on IE7 and the same thing occurs, anywhere from a slight delay to several seconds when paging.
Interestingly, I just tried the same Prometheus example in Firefox 2.0.0.11, and it was very fast. Could it be an IE7 issue I am seeing? I can get myself to an IE6 machine tomorrow and try again if that would help, but I definately see a difference between IE7 and Firefox as well as IE7 seems fine when I run the examples locally on my machine. Could it possibly be something with IE7 over the wire? Strange...
Thanks,
Chris
Interestingly, I just tried the same Prometheus example in Firefox 2.0.0.11, and it was very fast. Could it be an IE7 issue I am seeing? I can get myself to an IE6 machine tomorrow and try again if that would help, but I definately see a difference between IE7 and Firefox as well as IE7 seems fine when I run the examples locally on my machine. Could it possibly be something with IE7 over the wire? Strange...
Thanks,
Chris
0
Hello Christopher,
Based on the information supplied thus far, I assume this is a rendering issue, due to the IE7 browser. For additional information, I would suggest that you refer to the following article. Essentially, you can test the rendering after removing any css declarations(skins) and limiting the number of records rendered, to see which setup achieves the most optimal results. Additionally, you can also open a formal support ticket, and send us the problematic code, in the form of a small working project, which we can debug locally, and advise you further.
Greetings,
Yavor
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
Based on the information supplied thus far, I assume this is a rendering issue, due to the IE7 browser. For additional information, I would suggest that you refer to the following article. Essentially, you can test the rendering after removing any css declarations(skins) and limiting the number of records rendered, to see which setup achieves the most optimal results. Additionally, you can also open a formal support ticket, and send us the problematic code, in the form of a small working project, which we can debug locally, and advise you further.
Greetings,
Yavor
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
0
Christopher Blickley
Top achievements
Rank 2
answered on 15 Jan 2008, 03:15 AM
Thanks,
I'm going to drop the issue unless someone else chimes in that they are seeing the issue too when comparing the classic and Promtheus.
I'm not sure sending an example will help since the issue I'm seeing is on your site, not with something I'm working on.
Thanks,
Chris
I'm going to drop the issue unless someone else chimes in that they are seeing the issue too when comparing the classic and Promtheus.
I'm not sure sending an example will help since the issue I'm seeing is on your site, not with something I'm working on.
Thanks,
Chris
0
Hi Christopher,
The Prometheus version of the control has a number of optimizations and is faster than its predecessor. That being said, I believe that this has more to do with the browser rendering rather than anything else. I will investigate this issue further, provide you with the performance metrics shortly.
Greetings,
Yavor
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
The Prometheus version of the control has a number of optimizations and is faster than its predecessor. That being said, I believe that this has more to do with the browser rendering rather than anything else. I will investigate this issue further, provide you with the performance metrics shortly.
Greetings,
Yavor
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
0
Hi Christopher,
I did some further testing and found that the most probable reason of the delay is the redesign of the online examples, for the prometheus suite. Nevertheless, I made two samples, with the same basic setup, and with one using the standard grid, and the other one the Prometheus one. Attached to this message are the runtimes of both of the controls, showing the Prometheus control rendering a little faster than the standard gird. The setup uses 100 records. Althogh the precise figures may vary from setup to setup, there have been significant performance optimizations for the control (databinding and rendering), which are evident in many scenarios.
Regards,
Yavor
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
I did some further testing and found that the most probable reason of the delay is the redesign of the online examples, for the prometheus suite. Nevertheless, I made two samples, with the same basic setup, and with one using the standard grid, and the other one the Prometheus one. Attached to this message are the runtimes of both of the controls, showing the Prometheus control rendering a little faster than the standard gird. The setup uses 100 records. Althogh the precise figures may vary from setup to setup, there have been significant performance optimizations for the control (databinding and rendering), which are evident in many scenarios.
Regards,
Yavor
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
0
Mike
Top achievements
Rank 1
answered on 03 Jul 2008, 03:56 PM
What is the name of that tool you used to test the pages, where can I get a copy!
That is really COOL! Thanks!
That is really COOL! Thanks!
0
Darius
Top achievements
Rank 1
answered on 03 Jul 2008, 04:56 PM
Kind of related... a while ago I improved performance of one of my apps by intercepting the ViewState and compressing it as the page is loading.
See this article.
So, two questions:
1. Is Telerik doing anything similar with its controls?
2. If I compress ViewState, is it going to break any Telerik functionality?
Thanks.
--DT
See this article.
So, two questions:
1. Is Telerik doing anything similar with its controls?
2. If I compress ViewState, is it going to break any Telerik functionality?
Thanks.
--DT
0
Temp
Top achievements
Rank 1
answered on 04 Jul 2008, 03:26 AM
Hi Yavor, can you please tell us the tool you used in those screenshots you posted to time your page requests?
0
Hi Mike,
You can find more information on the tool used, in the following location.
Further, with respect to the ViewState compression, please refer to this post.
I hope this information helps.
Regards,
Yavor
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
You can find more information on the tool used, in the following location.
Further, with respect to the ViewState compression, please refer to this post.
I hope this information helps.
Regards,
Yavor
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
0
Mike
Top achievements
Rank 1
answered on 08 Jul 2008, 01:20 PM
Thank you Yavor!