This topic is locked
[SOLVED]

 RuntimeBinderException

10/2/2019 10:29:35 AM
ASPRunner.NET General questions
D
doofus5000 author

My .net application is very slow. Even a simple application with one table take 5+ seconds to load the initial page. When debugging in Visual Studio 2019 I noticed the 'RuntimeBinderException' was thrown hundreds of times for each page load.
Anyone else noticed this when debugging?

admin 10/8/2019

Runtime exceptions, while annoying, won't cause this sort of performance issue. Here are two possible reasons for performance issues.

  1. If this delay only happens once after new build/upload - this page is compiled the first time it runs and all subsequent loads will be fast.
  2. If this happens every single time - 99% of the time this is an issue with a slow SQL Query. Here is the article that explains how to troubleshoot it:

    https://xlinesoft.com/blog/2011/04/08/improving-perfomance-of-phprunnerasprunnerpro-applications/

D
doofus5000 author 10/14/2019



Runtime exceptions, while annoying, won't cause this sort of performance issue. Here are two possible reasons for performance issues.

  1. If this delay only happens once after new build/upload - this page is compiled the first time it runs and all subsequent loads will be fast.
  2. If this happens every single time - 99% of the time this is an issue with a slow SQL Query. Here is the article that explains how to troubleshoot it:

    https://xlinesoft.com/blog/2011/04/08/improving-perfomance-of-phprunnerasprunnerpro-applications/


Would this matter if 1 query was slow? I have a couple of queries that are slow but the majority of them are simple queries.

admin 10/15/2019

It looks like you are still trying to guess it. Pick one page that is slow, follow the advice from the article to print SQL queries on the page, run those queries manually etc.

Dalkeith 10/18/2019

Here's something that worked for MS Azure for me..
I went to Uptime Robot and signed up and then created a monitor looking at the application every 5 minutes.
First load after publication will be slow for each page that hasn't been opened as you are creating a cache on the server but after a form has been opened Uptime seems to keep the server from losing it out of the cache and everything seems to be good.
MS Azure also offer something called Always ON which I believe does the same but may not be available depending on what web app service plan you are on.
https://uptimerobot.com/

D
doofus5000 author 10/29/2019



It looks like you are still trying to guess it. Pick one page that is slow, follow the advice from the article to print SQL queries on the page, run those queries manually etc.


I try this on pages where the queries run in less than a second, the page still takes 5+ seconds to load

D
doofus5000 author 10/30/2019



Here's something that worked for MS Azure for me..
I went to Uptime Robot and signed up and then created a monitor looking at the application every 5 minutes.
First load after publication will be slow for each page that hasn't been opened as you are creating a cache on the server but after a form has been opened Uptime seems to keep the server from losing it out of the cache and everything seems to be good.
MS Azure also offer something called Always ON which I believe does the same but may not be available depending on what web app service plan you are on.
https://uptimerobot.com/


I ended up switching idle time-out on IIS to 0. That seems to help with some of the slowness. This should be ok as I won't have a high load on the server. (fewer than 20 users on the website)