Thoughts on copy2ram on machines with not that much physical RAM but with internal harddisk(s) with large native Linux swap partitions:
Would the performance of Porteus on such a machine profit when the modules got completely loaded not into RAM - due to not that much available RAM - but into the swap partition?
Especially when the boot device is a slow USB stick, and the swap device is on the much quicker internal hard disk partition?
If that would bring performance boost, how could that be implemented?
Aka is it possible to create a "copy2swappartition" cheatcode?
New features which should be implemented in Porteus; suggestions are welcome. All questions or problems with testing releases (alpha, beta, or rc) should go in their relevant thread here, rather than the Bug Reports section.
1 post • Page 1 of 1
- Posts: 2949
- Joined: 11 Jan 2011, 02:46
- Distribution: Porteus 5.0rc2 + 4.0 i586 XFCe
- Location: Forests of Germany