@lma
For most, (me including), ramzswap works OK, but doesn't offer any noticeable benefits.

As for ereswap, of course, it provides benefits - after all, "virtual" swap is a gain of only half of ramzswap size (so, for 64 MB ramzswap, You "gain" 32 MB at cost of CPU power), so fragmentation of "real" swap is only delayed.

It could be delayed further, if You would, for prolonged period of time, use less swap than ramzswap size (i.e, in above example, less than 64 MB) - as swap would be appearing and disappearing in environment, where fragmentation *shouldn't* be noticeable (it still occur, but is negated due to speed of RAM) - but every bit written to real swap, brings You closer to hitting painful fragmentation.

BTW, ereswap, by design, *does* consider, that only "real" swap should be counted for swap fragmentation - as long as in config file, You provide locations *only* for real swap (both main and backup), update rcS-late accordingly (via ereswap's scripts), and, if necessary, edit things to enable usage of ramzswap.

Just keep in mind that editing rcS-late by hand invalidate it for using adjust-rcS-late and update-rcS-late - yet, it's not a big deal, as if You know how to edit rcS-late by hand, You actually don't need those two scripts They're mean to "automagically" update rcS-late, saving it from users doing manual changes to file, that is critical for boot process.

/Estel