When I browse to a local site on IIS using Chrome I get intermittent slow performance.
It doesn't seem to matter whether the request is a full page request or an ajax request, it happens a significant percentage of the time, enough to slow down my development or make me use a different browser. Browsing to the same site in the live environment runs fine. Firefox and IE are running fine, just seems to be Chrome.
The network tab is showing the delay on the Blocking phase on my machine so I don't think it's a problem with DNS and disabling IPv6 didn't help me. Could it be something to do with the application or session cookies? I'm running Windows 8.1 with IIS 8.5 and the general performance of the machine is good.
Very frustrating because I prefer Chrome tools to the dev tools in other browsers and I've not had this issue on other dev machines where I've used Chrome.
Clear all your data (cookies, history and cache) if that doesn't work, reboot your PC, if that doesn't work, reinstall Chrome.
I hope it helps
Related
I have been facing some weird connection timeout issues in Visual Studio Code.
I am writing a simple web crawler to read a website using the requests and beautifulsoup4 packages in Python. I don't have any problem opening the URL in my web browsers (opens fine in Edge and Chrome), but when I say request.get(url), then the request always times out. Also, when I try to install some additional packages using pip, it always times out. But the corresponding PyPI page opens fine on my web browser.
The funny thing is - I am facing this issue only when I work out of my company's office. I don't have this issue at all when I am working from my home. There shouldn't be a system-wide firewall or a network firewall, because if there is, then the sites shouldn't be opening on my browsers too, right?
I went to VS Code Preferences and checked the settings there. There's no proxy set up. There is nothing specifically that would block network requests from inside VS Code. Here are some screenshots showing what VS Code Settings looks like.
I looked online and couldn't find much, since every question out there is regarding timeouts in SSH connections, which isn't relevant to me here. This official site here gives a bunch of URLs that need to be allowed by the firewall for VS Code to be able to connect to the network, but I don't know where to add them.
Is there something that I am missing? Any leads on how I can debug this issue? Or is it something that I'll have to take up with my company's network administrator?
TIA.
Working in the local environment I'm quite often getting errors on communication between the visual studio, IIS, IIS-Express and the browser (any combination). Everything is working on closing down the computer and doesn't any more when the computer restarts. Problems have started when the computer joined the domain.
I've spend hours searching for a solution to the problem. It looks as Widows Defender is to blame which is triggering different rules after I've joining the domain. It is enough to switch off the firewall, start any web application and enable the firewall. Simple (yet annoying) but working (what is most important).
I have run into a few cases where IE10, with Document and Browser Modes set to IE8, is unable to reproduce bugs observed in a genuine copy of IE8 on a co-worker's computer. For most IE version-specific problems, switching IE10 to IE8 mode allows me to recreate them just fine, but more than once I've had version-specific problems that only genuine IE8 can reproduce.
Is there any reasonably easy way to get IE8 on my computer without losing my IE10 installation?
(A "No" answer is better than a convoluted solution)
A "No" answer is better than a convoluted solution
Well, in that case, a "No" answer is what you shall get.
No. You can't.
Just for completeness, the "convoluted" solution:
Use a VM (Virtual Machine). This is the standard solution for testing with old IE versions.
You can download pre-configured VMs for testing every IE version from Microsoft's site http://modern.ie/
Alternatively, you might want to try out http://browserstack.com/, which is an online VM provider; same VMs as you can get from modern.ie, but running on their servers via your browser, rather than running it yourself on your own hardware. It's a paid service, but extremely convenient (oh, and you can get a free 3 month subscription from modern.ie)
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.