• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

How to improve performance using IIS6 / WIN/2003

P

phillydog

Senior member
I can run a website using WIN/XP Pro or WIN/2000 and the pages come up immediately. IIS is being used.

When using WIN/2003 with IIS 6, it initially takes a while for the page to load. Almost as if if the IIS was in a sleep mode. I have installed Apache on WIN/2003, and this doesn't occur, so as I think it is an IIS issue.

Someone mentioned TCP_DELAY generically, but I can't find this in IIS.

Any advice on how to give the same performance as WIN/2000 or WIN/XP pro would be appreciated.
 
I have a static HTML page that I can go to via http://boxname and I do this from another box or even on the box itself, and it may take (what seems like forever, but probably about 20-30 seconds) to come up. This is strictly a static HTML page.

I have other web applications on that box which take just as long.

But the catch is that once a page comes back (whether HTML, ASP, web app, etc....) all others are fast.

If I am on the box, I can do a 'netstat -an' and see it running, and looking at the processes within task manager, memory and CPU usage are low... nothing out of the ordinary.

If I do the same thing on WIN/2000 or WIN/XP pro, all is quick.
If I load Apache/Tomcat on another port (i.e. 81) it loads quick too. It is almost like IIS is going into sleep mode or hibernate (as is a choice for windows), but windows stays up, and only IIS is affected.
 
Funny you should mention this problem because I have the same thing happening with me. I'm running some small PHP scripts, but mainly just basic HTML stuff. The site is basically just my personal web portal. Running '03 Server with IIS6. I always attributed it to the harddrives sleeping. The OS harddrive never goes on standby, but the 2 other drives in there do and I figured for some reason IIS6 wanted the drives awake since they were referenced in links on the site(even though there were no active requests for those drives). Either way it doesn't bother me too much(the delay is only about 5 seconds for me, and then instant after that), but I'd be curious to see if anyone knows what the problem is and if there's a fix.
 
Originally posted by: winzonly
did anyone mention... Microsoft has the worst applications?

are you running a lot of IIS services?
Click to expand...

That's a pretty ignorant statement! Way to help the guy out.

Anyways... it sounds like your Application Pool is quiting after a set timeout. What app pool do you have the website too? Did you make your own? What are the settings of the app pool? The default app pool is set to recycle after 30 minutes I believe.

IIS6 is extremely powerful compared to IIS5. At the hosting company I work for we are able to run 450 websites that do significant amounts of traffic on a single dual CPU server using a NAS back end. Using application isolation the uptime of the server is determined on when we have to install patches. To me this is comparable to the uptime of my FreeBSD servers which also only to go down for patches. Of course MS does have a lot more patches, but I still believe the IIS6 is an extremely capable web server.

fyi, I run no MS software at home (9 computers). So I'm not some anti opensource troll or MS zealot. I base my opinions on knowledge and experience, not heresay and popular beliefs.

Oh, also this behavior is not a bug. It's a feature. It may not be needed for a dedicated website, but in a share hosting environment this feature is a godsend!
 
I have 2 websites within IIS, 1 a personal website which was previously hosted on FortuneCity.com, and one for my company's software, which isn't really memory, CPU, or bandwith intensive.

As I said, if I move this to Apache, all is fine.

On IIS, I am using the DefaultAppPool for the Application Settings, but since I am not using ASP, and get this when running a static HTML page, I do not think that this would be the cause of my issue.

I won't rule it out though.
 
It doesn't matter if you are running ASP. The App pool will still server static files.

Try the following:

Kill the w3wp.exe in Task Manager
Request an HTML file
Check Tast Manager to see if a w3wp.exe exists again.
 
I think I may have found the answer.

1.) Go into IIS 6.0
2.) Under the computer name, right click 'Web Sites' and choose 'Properties'
3.) Click on 'Service' tab
4.) Check the boxes next to 'Compress application files' and 'Compress static files'

This seems to have improved my response time greatly, and hopefully it will help you guys out too.. let me know if it works or not.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top