|
All kinds of things page out and in all the time. That's integral to the way the system is supervised. Many factors go into paging activity, but paging something out is not necessarily bad. If a process has X resources tied up and then runs off to do something that doesn't need those resources and is going to a long wait (or some such), why keep those X resources tied up and unused? Were it not for the paging activity, we wouldn't see many jobs being serviced at time. Gary Guthrie James Rich wrote: > > An array that is stored on disk is sign of a system that is not operating > efficiently (unless the array is consuming hundreds of megabytes). > Hopefully things other than disk accesses are not paged in and out of RAM > too often. If they are, you have more problems than just wondering > whether or not you should use an array.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
