Yesterday, April 1st, around 2:35PM Eastern, several of my web forms became extremely slow/non-responsive for a period of about 5 minutes or so. This also happened on March 14th. Since it happened so quickly, I could only do limited troubleshooting, but it seems like any of our forms that has a Radgrid became slow. One of our forms has been in use since last winter and has not been changed since last last year. Only a few hundred records exist in that database.
I tried to open the web forms in Edge, instead of Chrome, and sometimes the form would initially open. When I closed out and went back in, the form would become non-responsive. I have menus on my forms and those always loaded, but the grid did not. And then after a few minutes, everything started to work fine again.
We checked IIS and the memory seemed fine at the time of the slowness. We checked the error logs at that time of failure and did not see anything either. It was a bit tough to troubleshoot as it was relatively brief both times it happened.
Has anyone else complained about this? Maybe a recent patch could be behind this? I'm not sure what to think/try.
2 Answers, 1 is accepted
Hi Joe,
Thank you for the report.
We haven’t received similar performance reports, but we’ll continue to monitor for any patterns or related incidents. Based on your description, especially with the RadGrid being a common factor and the intermittent behavior across browsers, it could potentially be related to a front-end rendering issue or a temporary resource bottleneck, even if system metrics looked normal at the time.
We're not currently aware of any performance issues in the latest versions of Telerik UI for ASP.NET AJAX. Could you please let us know which version of Telerik.Web.UI you're currently using? If it's not the latest, we recommend upgrading to ensure you're benefiting from the most recent performance improvements and bug fixes.
Also, if the issue has happened again since your last report, please let us know - any recurrence could help us better isolate the cause. Given the intermittent nature of the issue, consider monitoring network traffic and server load during the slowness periods. There might be spikes in traffic or resource usage that aren't immediately apparent.
In the meantime, we recommend reviewing and applying the performance optimizations suggested here:
Please pay special attention to the Grids section in the article, as it may help address the slowdown you're seeing with RadGrid controls.
Lastly, we suggest checking the server and IIS logs again for any suspicious events or trends that may have been easy to miss during the brief occurrence.
We’re happy to help further as you investigate this — just let us know what you find.
Regards,
Rumen
Progress Telerik
Enjoyed our products? Share your experience on G2 and receive a $25 Amazon gift card for a limited time!
Rank 1
Hi Rumen,
We are using version 2025.1.218.462
The slowness happened even on a database with only 60 records, so I can probably rule that out too.
I did a little more troubleshooting after I posted this. And as I mentioned, it was hard to troubleshoot as it happened so briefly both times. But, we think it could be a reference to a 3rd party javascript reference that is not local. You mentioned that as a possibility in your response - something with rendering. We were able to re-create the slow/no load behavior exact when we put a block on calling that JS reference. And we did this test on forms that have and don't have the Telerik grid as well as forms that don't have this JS reference. So while I'm not 100% certain this JS reference is the issue, we are going to be mindful if this happens again on what forms to test(grid/no grid, 3rd party JS reference or none).
We're also going to try to reference any JS reference and Telerik references locally. Are there any drawback with calling Telerik references locally?
Hi Joe,
It's great to hear that you've narrowed down the potential cause of the slowness. Moving forward with referencing JavaScript files and Telerik resources locally is a solid strategy to improve performance and reliability. Here are some considerations:
Pros
- Hosting JavaScript files and Telerik resources locally reduces dependency on external networks, decreasing latency and improving load times.
- Local resources aren't affected by external server availability, crucial during network outages or external provider downtime.
- Local hosting allows more control over caching policies, updates, and versioning, tailored to your application needs.
Cons
- You'll need to manage updates and versioning manually, including downloading and deploying new versions.
- Hosting resources locally might increase server load, especially with large resources or high traffic volumes. Proper caching strategies can mitigate this.
Recommendations
Use RadScriptManager and RadStyleSheetManager: These controls can optimize script and style loading by combining them into fewer requests, improving performance. More details can be found here:
Enable Caching: Ensure effective caching of static resources on your server to reduce load and enhance performance for returning users.
Monitor and Test: Continuously monitor performance and test changes in a staging environment to ensure local references work as expected.
By implementing these steps, you should see improved performance and reliability in your web forms. If you encounter any specific issues or have further questions, feel free to reach out.
Regards,
Rumen
Progress Telerik
Enjoyed our products? Share your experience on G2 and receive a $25 Amazon gift card for a limited time!