Opened 14 years ago
Closed 12 years ago
#6923 closed enhancement (fixed)
Introduce a upper bound restriction, based on percentage of free space
| Reported by: | mmadia | Owned by: | leavengood |
|---|---|---|---|
| Priority: | normal | Milestone: | R1 |
| Component: | Preferences/VirtualMemory | Version: | R1/Development |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
Currently, VirtualMemory will not consider the amount of available free space after creating it's default sized swap file. For instance, on a 10 GiB partition with 4 GiB of memory, the swap file will be 7.99 GiB, often leaving less than 500 MiB.
Perhaps VirtualMemory could do some calculations to make sure that upon creating the swapfile, a minimum of 10-20% free space remains available.
To be clear, this is only for first creating the swap file (or anytime the user manually adjusts it).
Change History (2)
comment:1 by , 13 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:2 by , 12 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
This has pretty much been fixed by Alexander in hrev44611 and the other recent changes to the VM.
Note:
See TracTickets
for help on using tickets.
This has annoyed me before, so I'll take ownership.