Should a process be penalized for generating excessive page faults?
What will be an ideal response?
This is an interesting question, since sometimes excessive page faults are generated
because the operating system is doing a poor job maintaining a process’s working set in primary
memory. How do you define “excessive page faults” when there is no known standard
for page fault rates? This is something that depends on the characteristics of each individual
process.A high page fault rate could indicate a process that is poorly written, so it does not
exhibit locality. Or, it could be a well-written process that of necessity has a wildly dispersed
reference pattern natural to the application itself.A process could simply be transitioning
between major phases, in which case it will temporarily have a high page fault rate as it pages
in its new working set—this is perfectly normal behavior that the system should not penalize.
You might also like to view...
The ____ control can be used to send a message to each of the items in an array.
A. send items _ B. index iterator _ C. for each in _ D. while array _
What is wrong with this code?
```class CReceipt { private: float price; public: CReceipt(); CReceipt( float p); CReceipt(float p) {price = p:} }; ``` A. Nothing is wrong with this code. B. should not have a semi-colon after last brace. C. the constructor does not initialize private variables. D. There are two declarations for the overloaded CReceipt() function.
?_____ creates a complete set of technical specifications that can be used to construct an information system.
A. ?Systems design B. ?Systems investigation C. ?Systems analysis D. ?Systems development
In your report, comment on whether the offshore outsourcing of IT jobs is just another step in the progression that began with manufacturing jobs, or represents a whole new trend. Be sure to cite Web research sources and your own reasons.
What will be an ideal response?