I have a web app written in ASP.NET Web Forms which takes like 7 seconds to perform any anction.
The browser tools says that the loading time is spent to actually send the request, while to retrieve it is fine.
Here are a couple of screenshots
How could I test what's wrong other that that?
I have other applications coming from the same source code, and those works fine.
The webApp is running on a local IIS server (8.5) using a classic asp.net 4 app pool and is made in Visual Studio 2010 (althought I could test it with 2013 also)
I scanned the whole thing using Ants Performance profiler
but I found nothing.
Anyway I found the cause were a really simple query which should've returned back a single line..
The db wasn't properly indexed so it took forever to load
Removing that query solved the problem for me
Thank guys
Related
I'm running a .NET C# (4.5) web forms application and on our production server, the application gets slower and slower for everyone over time until about an hour where it becomes pretty much unusable and we just restart the server.
It works perfectly fine on my local machine. Never gets slower at all. So I'm trying to think of what would be different.
My local machine connect to the same database. There's also some active directory things being used for logins but that also connects to the same place on both my local and production environments.
I have debug off in the web.config. I've also looked up pretty much any other solutions and haven't had luck.
I did see some stuff about viewstates building up with ajax requests. I do have a page with updatepanels that are refreshing every few seconds, but I'm confused as to why the production server would be getting slower over time with this and not my local machine testing.
There's only about 10 people using the application at the moment also. Any ideas?
Refreshing a bunch of updatepanels every few seconds is not a good idea pretty much. I was able to optimize things here and there but in the end it was the auto refreshing that was slowing things down. Completely reprogrammed using signalr to grab updates and now it's very fast.
I'm working on a MVC .Net project that uses SignalR as a bi-directional communication between he client and server side.
Lately I've noticed that my CPU is getting overloaded quite quickly when I start the server (from visual studio). I looked around in task manager and seen that iisexpress.exe is consuming almost 90% of my CPU, and if I pause the project it shows that the server is idle and yet it's consuming all of my CPU.
I also tried to run the project on a much stronger PC, but the results were the same.
I read about this issue and saw this is a known issue which can be solved by turning off the browser link option, so I tried that, but not only that it didn't drop my CPU usage back to normal, but it also killed my connection between the server and the client side. Apparently this option is based on the SignalR technology, so by turning that option off I basically kill the communication between them.
I have three questions about it:
How can I solve this issue? turning off browser link doesn't work.
Will this problem persist even after I'll publish the project to the server? meaning it will run directly on the IIS server without VS in the background?
Is it not recommended to use SignalR on large HTML pages?
I would really appreciate your help!
I've been testing out CassiniDev server for a project I'm working on currently, and I've been so impressed with this!
Big well done to the guy(s) who made this!
I do seem to have a small problem though, and wondered if anyone else has encountered it and managed to resolve it...
I'm using the the CassiniDev-lib.dll in my WinForms C# (Net3.5) project to host my web server, I start the server fine with the following command:
_server.StartServer("C:\\www\\host\\test", 32500, "/", "");
I can navigate around my ASPX web pages with no problems in the forms WebBrowser control, but if I leave the Form running for a few minutes and return to use it the server doesnt respond?
The server is still in "started" mode, but if I refresh the current page or try navigating to a different one I receive the error:
This program cannot display the webpage
If I stop the server manually, then restart, it works again for a few minutes, then repeats the same error.
IIS is not running in the background or anything, tried diferrent Ports but still seems to happen.
Does anyone have any ideas/experience with this cool little webserver?
Thanks all!
I have sharepoint 2010 solution with 3 web parts, which connects to Microsoft Dynamics CRM, when I open one of three web parts on first time, they are very slow in being connect to CRM, after the first load everything works pretty quickly.
which could be the problem and what could be a solution to solve the problem?
Use fiddler to verify, but it sounds like this is related to the initial login/handshake.
I've written a 2-tier C# asp.net application.
Everything works OK, but if I modify the SQL Server data using the management console, the changes are not displayed on screen. It seems the application reads the data from a cached instance.
I have tried everything to make sure it's not a browser cache issue... the data remains static until I restart the app or restar the web site. even clearing IIS cache doesn't help. If the data is updated by the application, it works ok... Any info about a default setting on the EF that caches data automatically?
I'm running Win Server 2k8 and SQL Server 2008, but the problem was there also for SQL2005.
I have no experience with this, but maybe the SqlCacheDependency can help you.
See this article for more info: http://davidhayden.com/blog/dave/archive/2006/04/29/2929.aspx