| 56 | | tested with swapfiles larger than can be addressed in 32 bits. Some statistics |
|---|
| 57 | | for one test on a 32-bit PC with 1 gigabyte of memory: |
|---|
| 58 | | |
|---|
| 59 | | Number of swapfiles 25 |
|---|
| 60 | | Largest swapfile 5.6 GB |
|---|
| 61 | | Total swap allocated 44 GB |
|---|
| 62 | | |
|---|
| 63 | | In other words, applications on this 1 GB desktop computer took up a whopping |
|---|
| 64 | | (by 2005 standards) 44 GB of memory space without falling over. They weren't |
|---|
| 65 | | very fast, of course, having to swap so much; but they did keep running. |
|---|
| 66 | | |
|---|
| 67 | | After this point, when we tried to use up even more memory, the hard disk filled |
|---|
| 68 | | up with swap files so no more could be allocated. The program has provisions to |
|---|
| 69 | | deal with this case robustly and fairly gracefully. It does not like to leave |
|---|
| 70 | | you with a 100% full disk with no room to save your data. After we closed some |
|---|
| 71 | | of the running applications, swapspace started steadily decommissioning swap |
|---|
| 72 | | files before settling in a more realistic state. |
|---|
| | 58 | tested with swapfiles larger than can be addressed in 32 bits. |
|---|
