Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : Intel Corporation (INTC) -- Ignore unavailable to you. Want to Upgrade?

To: Road Walker who wrote (138285)	6/27/2001 5:55:24 PM
From: Tony Viola	Respond to of 186894

John, What is software "aging"? You know, like cheese or wine aging. ;-) Actually, I haven't heard this term before. Must be an IBM thing. Systems that get various changes put on them can end up being corrupted in some areas and eventually crash. I guess IBM has put in patrol mechanisms to keep track of possible problem areas that may accumulate and crash. I don't know what they mean by these being a major issue with Intel servers. Compared to what? Someone else with more SW background could answer this better, I'm sure. Tony

To: Road Walker who wrote (138285)	6/27/2001 6:57:14 PM
From: Saturn V	Read Replies (1) \| Respond to of 186894

Ref < Software Aging .....small programming errors may accumulate and absorb increasing amounts of a computer's resources, eventually leading to server downtime. > I do see this problem with Windows95/98. For example every application uses memory, and the application makes a request to the operating system for memory. When the application terminates, it is supposed to return all the memory it used back to the operating system, which can then reallocate it to other applications. However most applcations have bugs and not all the memory used is returned back to the operating system.Consequently after a while the operating system runs out of memory. This can also happen with other graphics resources. I am forced to reboot my Windows 98, every few weeks because Microscoft mail and some other applications have "memory and resource leaks". I thought that Windows NT, kept track of the memory allocated to an application and when the application terminated, all the memory assigned to the application was automatically returned to the system pool. Another aging process can be memory fragmentation. On a rebooted system large memory block requests are easily fulfilled. However after a while even if all the memory is returned back to the available pool, the available blocks are fragmented, and are not big enough to meet a large block request. Good operating systems are supposed to merge a deallocated block with any contiguous free block. Some operating systems dont bother, and you are left with a large number of small blocks as the software ages. I do not know all the limitations of Windows NT.