I have a local development webserver set up using Win7 and IIS7.
I often have to test the applications and websites I develop on all browsers using "very slow" internet connections to determine how all the clients scripts execute and if the images and all linked resources load properly and in order on all browsers.
Now, this involves deploying the project to a remote server and then testing over a slow internet or network connection. In my case this is usually only possible at the end of the project. Its a pain to deploy the project every now and then only for speed testing ...
Is it possible to slow down IIS so it behaves like you're connected over a very slow internet connection and test the applications that way. This will also help me test the applications on a standalone PC (without a network of PCs) like on a home desktop that doesn't have a network connection only an internet connection.
Sorry for sounding newbie-ish ! ... couldn't help because I am one :)
Thanks, Norman.
UPDATE: Almost all answers to this question were great and work in different situations .... for me (IIS7 on Win7) the selected answer is the most appropriate ... I'm sure you'll find an answer here that works for you :). So thanks to everyone ... oh ... and don't be surprised if the next version of IIS or VS ships with magnets ! :D
An IIS or ASP.NET hang can cause your website to have slow page loads, timeouts, or 503 Service Unavailable errors. Hangs can be caused by blocked ASP.NET threads, bad configuration, or request queueing.
Fiddler has an option to throttle speeds locally as well which might be a bit more convenient.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With