Does restarting desktop each day have any adverse impact?
This is page 2 of the discussion. Read the opening post
Desktop
This is page 2 of the discussion. Read the opening post
by kevaburg
by kevaburg
In S3 standby power is only supplied to the memory bus and therefore the remainder of the computer can cool down.
The sort of thermal distortion that we are talking about could occur if S3 is not configured correctly resulting in the hot and cold environment we are talking about.
by archangel999
Letting the machine "sit for an hour" doesn't alter the dynamics of page caching.
Cached pages are recycled as/if needed, not on a timer. Virtual memory management still basically works like it did in the VAX/VMS days (from which Dave Cutler and crew ripped off most of the original Windows NT).
I use loads of different apps over and over again all day long on a machine with a 2GB footprint - video editing, graphics, Visual Studio, MS Office, IE, etc. and NEVER have to reboot.
On the other hand, I have seen PCs that are using crappy network or printer drivers, "acceleration" software, or just plain malware that will chew up physical memory overtime.
by archangel999
All I can tell you is that I'm currently at a client with hundreds of XP workstations - NONE of which are being rebooted and NONE of which have any problem. In addition, my primary workstation (which is used for everything from MS Office to Visual Studio to Video Editing) was last rebooted about 3 months ago when I added a disk drive - my XP notebook is similarly NEVER rebooted (just put into standby or hibernate) - and even an old W2K workstation I use as a performance testing benchmark hasn't been rebooted in about six mnnths.
And NONE of these machines exhibits the behavior yuo describe.
Can't speak to the WNT since I haven't used a machine with that in years and W95/98 aren't even using the same architecture - so it's moot to discuss them.
However, the condition you describe can easily result if you're using one or more of the many crappy network/video/etc. drivers or if you've got some of the flaky network service software that many DSL and cable internet providers insist on pushing onto your machine.
by acsmith
by tayiper
Oh well, you are or course totally right, my bad!! You see, I mis-understood/mis-read the whole thing, i.e. I was thinking about "shutting the PC down" vs. "running non-stop" and not "restarting" vs. "running non-stop" as the topic really is all about.
best regards,
Ivan Tadej, Slovenia
by onbliss
and handled by the OS in most other Operating Systems, I say most as I haven't tried every other OS - but those I have tried do have a function that monitors what memory is used by what application and clears the memory when the application closes.
But regardless of blaming the application or the OS, MS writes both and they intend their applications to only be used on Windows, so they should have such a routine in one or the other - yet they have it in neither. Thus, QED, MS is to blame either way.
edited to fix typo that changed the meaning of the sentence - amazing what a missing 'e' can do.
by acsmith
By the way you are to be commended for your search for knowledge in the field of Information Technology. It can be both a rewarding hobby and a stepping stone to new career opportunities. While I have been an IT professional for 15 years I started as a PC hobbyist in the early 80's although professionally, at the time, I was a technician working with both analog and digital control circuitry.
Just be aware that there are as many "urban legends" in the IT field as any other area of life. Just because someone states something on the web or even in commercial PC publications doesn't necessarily make it correct. Discernment and critical thinking must still be applied.
As a server administrator I really hated having to my servers go full cold because of the difficulty of getting old SCSI drives to spin back up correctly. On the other hand I routinely shut down, when not in use, the business and personal desktops/notebooks for which I am responsible and they last as long or longer than those run continuously. I am exposed to systems operated in both environment.
by tayiper
Thanks for the nice and very true words, acsmith !!
best regards,
Ivan Tadej, Slovenia
One improvement in XP over the earlier MS Windows, is that it'll move things from RAM to VM more readily, and will keep expanding VM while there's space on the drive. If your system has lots of RAM and free space, you can go a long time before it finally has a hernia, but the amount of space used by VM will grew.
I wish I had DSL, remote rural phone line - can't handle broadband at all, not even ISDN.
Edited to correct typo - seem to be dropping a lot of 'e's lately
by archangel999
So are you saying that your Commit Charge Total is always sitting at or near the Commit Chart Peak - that would mean VM was going unreclaimed (not likely) or you've got one or more system-level components like service, driver, background process (e.g., anti-virus) etc. (that don't ever shut down that continue to allocate more and more VM) - that happens a lot with certain defective network drivers and some bloatware from McAfee and Symantec
Remember Occam's razor
would have VM constantly growing. You can view this in the Task Manager, once you have the window set to show VM.
The problem only ever related to processes related to Windows, or other MS software. Open MS software and you see new processes open. Close the app, and some, but not all the processes it opened, will close. Run apps like MSIE and the VM keeps growing, even wehen you just leave the window open in the background. MSIE and Outlook Express are the worst culprits for this. the real beauty is OE, open it, and regardless of how you have any other service settings, it will enable and open messenger (the service), and leave it open. Close the process, and reset the service to disable, and OE will re-enable and open next time you use it. That's why I dumped OE two years back, went to Fox Mail, uses less resources, and has higher security as well.
Don't use McAfee or Symantec on my main machine, haven't for years.
I've only ever seen the problem occur with MS apps, nothing else. Stopped using them and the situation improved. Dumped OE, dumped MSIE, dumped MS Office, and the system performed a whole lot better. But it should perform well regardless, just poor design in the OS by MS, and ditto in the apps.
This discussion is closed to new replies.
Sort by Trending