Ask stupid questions and you'll get a stupid answers, was: Technological advantages over Linux
aryeh.friedman at gmail.com
Sun Jul 26 13:59:35 UTC 2020
On Sun, Jul 26, 2020 at 9:57 AM Aryeh Friedman <aryeh.friedman at gmail.com>
> On Sun, Jul 26, 2020 at 9:55 AM Steve O'Hara-Smith <steve at sohara.org>
>> On Sun, 26 Jul 2020 09:04:02 -0400
>> Aryeh Friedman <aryeh.friedman at gmail.com> wrote:
>> > On Sun, Jul 26, 2020 at 8:43 AM Steve O'Hara-Smith <steve at sohara.org>
>> > wrote:
>> > > Here is a variant of your experiment that should demonstrate
>> > >
>> > > 1: Reboot machine, measure performance
>> > > 2: Memory stress machine to until swapping reduces performance
>> > > 3: Kill memory stressing process
>> > > 4: Disable swap - which forces all pages back into RAM
>> > > 5: Enable swap
>> > > 6: Loop to 2
>> > >
>> > Since stealing memory from a running process that counts on it to be
>> > functional will crash the process and odds are that process is something
>> > low level and critical to keeping X running the above variant is not
>> > practical to do and thus my current solution has the same effect --
>> > reboot.
>> It is very practical and it is the way I normally recover a system
>> from a memory usage spike, it works far better than just leaving it alone.
>> Nothing in that steals memory from running processes.
> Unless there is just not enough RAM to allow all the pages to be recovered
> which as far I can tell is the problem.
sudo swapoff -a
sudo swapon -a
Result: Firefox froze up
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
More information about the freebsd-questions