Restarting Servers

Its not about windows being stable, its about the poor code some people write which causes problems.

I'm not pointing fingers but simple things like closing your database connections properly can make a difference. We have 1GB to 2GB of ram on each of these servers. Nonetheless, we need to restart once in 2 or 3 days because the RAM fills up.
 
ya, poorly written code is definately a reason for unstable servers.. i have tried this myself on my own computer.. forgot to move to the next record in a recordset when looping through it.. filled 1GB of RAM and 2GB of Virtual memory in 20 seconds.......

i think jodohost does a good job at this part.. the windows servers on my last host is unavailable in norwegian office time.. get script timeout on pages with almost no script, page generation time on nearly a minute etc..

another reason is big access databases........... pain in the a$$
 
"60 second Reboot, Win2000?"

WOW, what servers do you have? Most servers I have seen can take 2-3min at least.

Hosting sites that have custom code from "DIY" coders can often run into these problems with poorly written code. I know MS is partially responsible but not completely. Try leaving the .asp and .net services off a server and see it you have to reboot as much.
 
Yash said:
Its not about windows being stable, its about the poor code some people write which causes problems.

I'm not pointing fingers but simple things like closing your database connections properly can make a difference. We have 1GB to 2GB of ram on each of these servers. Nonetheless, we need to restart once in 2 or 3 days because the RAM fills up.
Click to expand...

Speaking of poorly written code that affects other websites on the same server... have you guys looked any more into getting Win 2K3 servers back up and running? One of the new features of 2003 server is code isolation, where one man's (or woman's) bad code won't affect the rest of the code on the server...
 
This thread is very old. We put much more RAM on the servers now and rebooting a server because of low RAM has never been the case with us

Yes, we are exploring Win2003 again. We faced alot of problems with it earlier but most of them now seem to have been caused by HSphere 2.3. HSphere 2.4 seems to be working much better with Windows 2003.

But we will not be upgrading any of our windows2000 servers. They are performing very well and upgrading OS would be very painful procedure.
 
Yash said:
But we will not be upgrading any of our windows2000 servers. They are performing very well and upgrading OS would be very painful procedure.
Click to expand...

Sounds good to me! Don't ever want to go there again. :]
 
Something that might help is cacheman, you can download it for free and stick it on the servers. It has an optimization it adds into windows that unloads inactive dll's from memory, and it can also be set to recover system memory when it drops below a certain amount. It doesnt free up as much memory as some other applications out there, like taskinfo, but it'll do the job. Taskinfo is another good app to have on the servers. It lets you see the details of the processes running on a machine, and gives you the ability to flush a processes memory out. It can also flush the system file cache, and do an extremely thorough job of freeing up system memory. With a 512mb ram system, i've seen it free up to 440mb(on a cpu running for over 7 days straight)...now thats hardcore. Between those two apps, you should be able to restore performance to a server, just like how it runs when you reboot it. Thats been my experiences with those atleast. You guys should test the combo of those two apps on a server. At the least, they'll give you a slight performance boost with no loss of system stability.
 
You must log in or register to reply here.
Back
Top