Joe, I wasn't mocking you. Wasn't even "mocking" asinoro ~~ I refrained elsewhere from posting to counter his "tip" (if it works for him, um... bless his heart, but I'm uncomfortable seeing that "tip" stand unchallenged). I was pointing out that even though you've provided plenty of details (including some superfluous considerations, like cpufreq) your successful troubleshooting will probably require tweaking/retesting of numerous factors, one-thing-at-a-time. Specific to swappiness... based on my prior testing, I was suggesting to set swappiness to 1 (NOT 90, as you may have read as a "tip" elsewhere in this forum).
it is not quite clear whether the value you have to change is in microseconds or miliseconds. I'll try it out anyway (using 60000).
I included that detail in my earlier post "milliseconds... I set mine to 120000 (two miniutes)
but understandably easy to overlook that among the "too many words".
never totally understood the "persistence" concept
During a liveboot session, we're dealing with a "layered filesystem".
First, a base layer, populated from the content read from the linuxfs file is generated, then
if dynamic root persistence was requested (otherwise, skip this step),
a layer populated with the content of the rootfs savefile (perhaps currently empty/blank) is added atop the first, then
Finally, a blank layer which will serve as a (writable) session scratchpad is added atop the stack.
Throughout the session, in response to each file read/write request:
If home persistence was requested, and the affected file is pathed under /home, it is DIRECTLY read from, and written to, homefs storagefile
(else if) STATIC root persistence was requested, the changed file is directly, immediately, written to, rootfs storagefile.
Otherwise, the filesystem "consults the stacked layers".
When a file residing in the stack is modified (created, edited, deleted) during the session, that change is recorded to the top layer.
Each time the filesystem "consults the stacked layers" to retrieve a file, the record in the top layer takes precedence.
If a requested file is present (AND has not been "marked deleted") in the top layer, the filesystem retrieves it and.. done.
(else if) it is present in the populated-from-rootfs layer (AND is not "marked deleted") the filesystem retrieves it and.. done.
(else) the filesystem retrieves the file from populated-from-linuxfs layer (OR reports "file not found")
During a "persist-save" operation, the content of rootfs file is updated (is `rsync` -ed) to match the current state of the top layer.