Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Arno Welzel Newsgroups: comp.mobile.android Subject: Re: What is your experience with Samsung "RAM Plus" virtual memory expansion? Date: Sat, 7 Dec 2024 13:51:45 +0100 Lines: 31 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Trace: individual.net x3vEm/NIsexch/0VSblQoAD/2A5SxCWfgmunyXQ2dSum4g9vgL Cancel-Lock: sha1:4aMKaOaqUaYUs3OqPPHVOfpV94U= sha256:Y5czCL4UGj++LjYpTIWOVGeKJkxcqiMR1CbLSCEQ/CA= Content-Language: de-DE In-Reply-To: Xref: csiph.com comp.mobile.android:145024 Frank Slootweg, 2024-12-06 12:51: > Andy Burns wrote: >> Edward.C wrote: >> >>> I think it depends on your usage. If you always have many apps running >>> at the same time, maybe it can give slight improvement in performance. >>> >>> I have disabled it and never noticed any difference, probably because I >>> have 12GB of RAM on my A55. >> >> Given the way Android apps save their state and are then ready to be >> killed when there is pressure on memory, ready to be reloaded "as they >> were", then using swap seems a bit pointless? > > Yes, but not all apps can be killed and reloaded/restarted "as they > were". For example those which depend on external data or/and state. For > those apps, you want them to be swapped instead of killed. By definition an app *must* support the fact, that it can be killed at any time. Even rotating the display will kill and restart the current running activity. That's the reason, why dialog boxes should not be used but UI fragments instead since the state of fragments will be handled by the OS instead of the app. But on the other hand it depends on the app developers how good the implement state changes. -- Arno Welzel https://arnowelzel.de