What is the primary cause of thrashing in an operating system?
Think about what happens when memory is overused and the system spends more time swapping pages than executing processes.
Thrashing happens when the system spends most of its time swapping pages in and out of memory because there isn't enough physical memory for all active processes. This slows down the system drastically.
Which of the following best describes the working set model in operating systems?
Consider how the model helps decide how much memory a process needs based on recent activity.
The working set model keeps track of the pages a process has used recently (within a certain window of time or number of references) to estimate how much memory it needs to run efficiently without causing thrashing.
If a process's working set size suddenly increases beyond the available physical memory, what is the most likely immediate effect on system performance?
Think about what happens when memory demand exceeds supply suddenly.
If the working set size grows beyond available memory, the system must swap pages frequently, causing thrashing and slowing down all processes.
How does the working set model influence the choice between local and global page replacement policies?
Consider how keeping a process's recent pages in memory affects performance.
The working set model favors local page replacement because it tries to keep the pages a process currently needs in memory, which helps prevent thrashing by not evicting those pages to other processes.
Consider a system using the working set model for memory management. If multiple processes simultaneously increase their working set sizes, what is the most likely system-wide consequence?
Think about what happens when many processes need more memory than the system has.
If many processes increase their working sets at once, the total memory demand can exceed physical memory, causing thrashing and severe performance degradation.