Eric Skaggs
Top achievements
Rank 2
Rank 2
Eric Skaggs
asked on 19 Feb 2009, 06:59 PM
Just looking for some ideas here.
I do all my development on a local stand-alone server. I just downloaded and installed the 2008.3.1314.35 version of the assembly and have it working locally without any problems. In fact, it's actually alleviated a performance issue I had: with multiple grids and other controls on the page, I could click the insert button on the grid to open the edit form template, but the browser seemed to lag for about 5 seconds after the form showed up; I couldn't do anything. Upgrading to the 2008.3.1314.35 version fixed that for me locally.
I then built a solution package and deployed the exact same source code (that references the 2008.3.1314.35 version of the assembly) to my development machine (where end users can do some testing) and everything works fine except that now the performance issue IS NOT fixed there. On this dev server, I made sure the old version of my application was fully uninstalled and cleaned up all files left over by it...including the GAC and the WSS virtual directory's bin folder. I then deployed my solution, using the same settings in web.config and global.asax as I am locally, using the same 2008.3.1314.35 version of the assembly, but I'm now having trouble with performance on the development server. The versions of IE are the same.
Anyone have an idea?
Thank you,
Eric Skaggs
I do all my development on a local stand-alone server. I just downloaded and installed the 2008.3.1314.35 version of the assembly and have it working locally without any problems. In fact, it's actually alleviated a performance issue I had: with multiple grids and other controls on the page, I could click the insert button on the grid to open the edit form template, but the browser seemed to lag for about 5 seconds after the form showed up; I couldn't do anything. Upgrading to the 2008.3.1314.35 version fixed that for me locally.
I then built a solution package and deployed the exact same source code (that references the 2008.3.1314.35 version of the assembly) to my development machine (where end users can do some testing) and everything works fine except that now the performance issue IS NOT fixed there. On this dev server, I made sure the old version of my application was fully uninstalled and cleaned up all files left over by it...including the GAC and the WSS virtual directory's bin folder. I then deployed my solution, using the same settings in web.config and global.asax as I am locally, using the same 2008.3.1314.35 version of the assembly, but I'm now having trouble with performance on the development server. The versions of IE are the same.
Anyone have an idea?
Thank you,
Eric Skaggs
3 Answers, 1 is accepted
0
Hello Eric,
A possible reason for this problem could be JS code running after the page is rendered.
Can you provide us some statistics, about this delay? You can use Fiddler to get them. You can also provide us a live URL to see this page. Thus we will do our best to find an answer/fix for this erratic behavior.
All the best,
Georgi Krustev
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
A possible reason for this problem could be JS code running after the page is rendered.
Can you provide us some statistics, about this delay? You can use Fiddler to get them. You can also provide us a live URL to see this page. Thus we will do our best to find an answer/fix for this erratic behavior.
All the best,
Georgi Krustev
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
0
Eric Skaggs
Top achievements
Rank 2
Rank 2
answered on 23 Feb 2009, 08:04 PM
Unfortunately I cannot provide a live link to the site...it's not publicly available. I've downloaded Fiddler though. What types of statistics should I send you from Fiddler?
0
Hello Eric,
You can send us the whole captured information (attached in a regular support ticket) in one zip archive. When you start Fiddler, delete all received information and open the problematic page. The Fiddler will capture all requests to the server. Then you can save the session in a zip file.
It will be helpful if you send us the rendered mark-up code as a text file as well.
Kind regards,
Georgi Krustev
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
You can send us the whole captured information (attached in a regular support ticket) in one zip archive. When you start Fiddler, delete all received information and open the problematic page. The Fiddler will capture all requests to the server. Then you can save the session in a zip file.
It will be helpful if you send us the rendered mark-up code as a text file as well.
Kind regards,
Georgi Krustev
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.