Opened 14 years ago

Closed 14 years ago

Last modified 9 years ago

#4 closed defect (duplicate)

Better eviction policy

Reported by: jtv Owned by: somebody
Priority: normal Milestone:
Component: component1 Version:
Severity: Ugly Keywords:
Cc:

Description

Is there a better way to chose which swapfile should be decommissioned? One criterion is that we want to get back to our target state; the current greedy algorithm (pick largest swapfile <= ideal size) is the best way of achieving that. But we may want to minimize resulting swap activity instead. In that case we could pick the least-used swapfile.

Since swapfiles have different sizes, it's not so easy to make an initial selection based on size and then use usage as a tiebreaker. A compromise between them perhaps, such as picking a range of "good" sizes first and then choosing among them based on usage?

Change History (2)

comment:1 Changed 14 years ago by jtv

  • Resolution set to duplicate
  • Status changed from new to closed

comment:2 Changed 9 years ago by jtv

  • Severity changed from normal to Ugly
Note: See TracTickets for help on using tickets.