Ref: Slow serving Ajax / Images, IIS 7.5 / .net / Windows 7
The question linked above describes the symptoms I am seeing exactly.
Using TFS2013 or SmarterTrack 9.5 on Windows Server 2012 R2 with IIS 8.5.
When I first load a page from either application everything seems fine and works fine for a little while. After locking my PC and coming back later any pages in either application will no longer load.
The progress indicator on the browser tab shows that it's still doing stuff but the images never load.
Closing the browser and re-opening resolves the problem temporarily but it will return when the session times out again.
Does anyone know a pure server config solution to this problem?
Related
I'm having a bit of problem debugging in VS for our web application, basically all requests are painfully slow, requests that used to take <1s are taking over 15s which as you can imagine makes developing a nightmare!
This is on my newly installed laptop (done it twice recently and the problem is the same both times on both laptops).
I've tried the following without success:
Run without debugging (ctrl+F5)
Run in release mode
Disable diagnostics panel in VS
Disable unused debugging options in VS
Different browsers (Chrome, FF, Edge)
Disable Antivirus
Disable ReSharper/Uninstalled
The solution is a mix of WebForms, MVC, WebAPI, Classic ASP with standard SQL connections (calling stored procs) and Entity Framework.
I have also tried Visual Studio 2017 and I'm getting the same issue there too.
Does anyone have any idea what could be causing it? I've googled and tried several things people have suggested without any success.
It turns out that the issue was down to have the Data Source value of the connection string set to (local), where as on my old laptop I know that in some instances this was set to the computer name.
I'm not sure which connection string was a fault as we have several in a fair few config files (about 20 connection strings in total) and I just changed them all.
However I'm still unsure why there is a noticeable difference in using computer name and (local) in this situation.
I just upgraded from a Windows 2003 Server (IIS 6) to a Windows 2012 R2 (IIS 8.5). I don't think it matters, but I also upgraded from ColdFusion 9 to ColdFusion 11. All of a sudden images would show as missing. For example, in the search results, the image with the first result will be broken. When I refresh the page, it is there.
I just can't figure it out and our Marketing VP is getting a little antsy... understandably so.
I view the source and the image path is correct. I even copy and paste it into the browser and the image shows.
Has anyone else experienced this? I appreciate any advice you may offer.
Take a look at your browser's Dev Tools (this is from Chrome). There should be a Network panel that will show all the images being loaded on your site. If there are any real missing images, you'll see a status of 404 (Not Found), otherwise you should see 200 (OK) or 304 (Not Modified). You'll also see a time column that can tell you if any images are just taking some time to load.
If you're directly showing the image on the page simply by sourcing the image file itself, then your latency shouldn't have anything to do with ColdFusion.
<img src="/path/to/some.jpg">
But if you're loading the images using cfcontent, then you need to figure out what's going on in relation to ColdFusion.
<img src="/path/to/some.cfm?fileID=1234">
Our upgrade from CF 9 to CF 2016 with an upgrade to Windows server on the 2016 boxes is in our Beta environment at the moment and we haven't seen any issues related to loading files (jpg, gif, doc(x), xls(x)) via cfcontent.
I finally figured this out. On our 32-bit 2003 servers, we had to use the Ionic Rewriting tool. Great tool, truly. I installed that on our new 64-bit 2012 server (yes, I used the new 64 bit version). I really don't know why, but when I installed thet Microsoft IIS rewrite module, wrote the filters and uninstalled the Ionic ISAPI filter... voila! The problem went away. I guess the Ionic rewrite tool doesn't play as well with IIS 8.5 as I'd hoped.
I'm having a performance problem on my company's web site using a specific version of IE 8 to load a page using https. Here's what I know.
Server:
Virtual machine running on VMWare ESX
Windows Server 2003 Enterprise Edition SP 2
Tomcat 6.0.16
Client:
Windows XP and Window 7
Internet Explorer 8.0.7600.16385IC
Page loads/refreshes in under 1 second using HTTP.
Page loads/refreshes in 15-16 seconds in HTTPS using this version of IE.
Problem reproduced on multiple client machines with same IE version.
Problem reproduced on multiple client machines with different Windows versions (XP and 7).
No performance problem using Chrome, Firefox, Opera, or Safari from same machine.
No performance problem using other versions of IE 8 on other machines.
Slow load causes virtually no CPU, memory, or I/O spike on server or client machine.
No performance problem on other sites using HTTPS on same client machine.
The pages in question use JavaScript and innerHTML to replace the contents of div elements to create a collapsible menu, and an iframe to display some content. A couple of the div elements contain images. If I remove the iframe and the JavaScript, the performance issues go away. However, rewriting the entire site to make these changes would be very time consuming. We're in the process of replacing the whole site, but it may be 2-3 months before we do so and we really cannot live with this slowdown that long. I've already looked at several IE tuning options, such as disabling add ons, running IE-rereg, and resetting IE, with no luck.
Does anyone have any suggestions?
The version you mention is the version that shows in Windows 7, is it not (i.e., in Windows XP, it should show like 8.0.6001.18904)? Have you applied all recent patches? More particularly, have you applied the KB980182 security patch?
That particular patch was an "out of band" patch, which means it has been brought to the public in haste and outside of the normal upgrade cycle. It came out April 22, 2010, or about. If you have installed the patch (either automatically, or by hand), try uninstalling or rollback using the Backup and Restore Center and select the restore point that mentions that fix.
While KB980182 caused quite some trouble and weird behaviors, you may try the same approach with other patches if rolling back to before KB980182 didn't help: rollback using Backup and Restore Center to an earlier moment in time, and check if the problem goes away.
This type of testing is a nuisance, I know, but I'm afraid there's little else you can do.
I've just installed Windows 7 x64 Ultimate on my desktop PC. I installed IIS, Visual Studio 2008, registered ASP.NET, etc.
I have this ASP.NET 3.5 website I'm working on running EXTREMELY slow on this new IIS. On STA and PROD servers (Windows 2003 Server) and on my old XP/IIS 5.1 everything runs smoothly.
A page which usually takes 1-2 seconds to load is taking 8 seconds!!!
I saw this post on IIS forum. It says something about Vista/7 not pooling connections (just to let you know, the website is running locally but it's connecting to a SQL Server 2005 hosted on a remote server).
It seems that it takes a while to "start loading" the page... I mean, I click refresh and it stays for several seconds "Waiting for localhost"... Then when it gets response it loads the whole page normally...
I don't have a clue how to force Win7/IIS7.5 to pool database connections.
EDIT: I've created a new empty ASP.NET web application to see if the problems happens too. The answer is no, it responds fast as it should with an empty default page. Maybe is something related to the DB connection. I will do a further test. It should be a way to fix it...
EDIT 2: Debugging the app I noticed that the delay occurs AFTER the execution of .NET code (Page_Load, etc)... so the delay seems to be somewhere when IIS serves the page to the browser.
For those having the same problem, here's two possible solution.
1) Disabling IPv6 support in Firefox (only for Firefox)
Most of the authors that I found out about suggest this approach as quickest and cleanest solution. What you need to do is basically to open configuration settings in Firefox (about:config) and to change network.dns.disableIPv6 setting to true.
2) Change localhost settings in your hosts file (all browsers)
This came to me as an idea to check where and how can I interfere in IPv6 settings on my machine. I saw one of the comments on above mentioned sources saying that one can get rid of the problem by simply replacing localhost with machine name in the url.
It didn’t take me long to check and see that disabling my IPv6 localhost lookup does the same thing as disabling IPv6 directly in Firefox.
What you need to do is basically to comment / delete this particular line in your hosts file:
#::1 localhost
Note: ::1 notation is IPv6 equivalent of the IPv4 127.0.0.1 lookup address.
I believe the second solution might be more suitable for users who do not want to disable IPv6 in general, and the first one for all others that still do not use IPv6 in their regular work.
I was having the same issue: extremely dead slow site performance using IIS 7.5 on Windows 7 64-bit with a Core 2 Duo with 4GB RAM and 3 Application Pool Processes running only 1 website. Here's what I did to get the speed back to IIS, problem solved...
The trick for me was to run IIS using 32-bit workers, as instructed by Microsoft on IIS.net, which you can read here:
http://learn.iis.net/page.aspx/201/32-bit-mode-worker-processes/
Simple solution provided (I don't want to rewrite it here)... Either you can run a 1-line command from the Windows Command Prompt or a 1-line command from Windows PowerShell. I just ran it from the command line (make sure you open Command Line or PowerShell as Administrator -- right-click > Run as Administrator).
Thanks,
Marty McGee
You can try running multiple processes as application pools:
Open IIS
Click Application Pools
Right click the app pool for your app
and click Advanced Settings
Find the
"Maximum Worker Processes" and update
it to 3 (or the number of processes
you want to allow to run).
I know the op was running IIS 7.5 and this may not apply to him, but I'm posting this as it might help others running IIS Express 8.0. I had the same problem and none of the IPv6 or hosts file changes worked for me. My asp.net MVC4 project was really slow after hitting F5 to refresh js changes on localhost. It was happening across all browsers - Chrome, FF, and IE. Eventually I discovered that IIS Express 8.0 is extremely slow when serving up js files and seems to be a bug. If I ran iisexpress on the command line and hit F5 I could see each js file took 4 or 5 seconds to load.
I ended up uninstalling IIS 8.0 and installing IIS express 7.5 and straight away the problem was fixed. Here are the steps I followed:
Uninstall IIS express 8.0
Delete the IISExpress folder (on Win 7 it's in My Documents\IISExpress)
Install IIS express 7.5 (Link to IIS Express 7.5 download)
IIS Express 8.0 seems to be installed with VS 2012 so if you had a new install or possibly a service pack update this might upgrade the previous IIS Express version.
I have a asp.net 3.5 web application which is deployed on server 2003 and IIS 6. After running fine for a few weeks it goes "Down" and by down I mean that when I try and access it the browser looks like it's loading but never actually serves the page. After an IIS reset it loads quickly again.
My question is what are the steps and tools I should use in tracking the root cause?
First point of interest would be the event viewer, second the iis logs. If you still do not find the error then performance counters could help you out there.