> may be different for GNOME with JIT'ed code
> potentially getting swapped out

How to recognize JIT'ed code? Do you mean that we shouldn't lock it?

пн, 14 сент. 2020 г. в 20:17, Benjamin Berg <bberg@redhat.com>:
On Sun, 2020-09-13 at 16:47 +0000, Alexey Avramov wrote:
> > So with
> > applications started, you might get higher.
>
> I think we should protect only basic GUI. On computers with 16G+ RAM
> locking 1G memory with apps should not be a problem if it helps to
> improve responsiveness.

Yup, fully agree. We only need to make sure the user remains in
control, we don't need to save random apps.

> > Was that with or without swap?
>
> It was without swap, but with swap it has the same effect (faster
> killer coming and system reclaiming) + responsiveness was improved
> during heavy swapping.

Yeah. I think things may be different for GNOME with JIT'ed code
potentially getting swapped out.

> > I feel that uresourced is just nicer conceptually.
> > So uresourced is
> > going to be ineffective for KDE for the time being.
>
> However, the advantage of prelockd is that may be used on old systems
> with any DE and any file system and an init. On Debian 9 Mate locking
> 150-200M takes very good effect. On Fedora with LXDE 200M is also
> good value.

Entirely true. I just personally prefer aiming for the long term here.

Benjamin
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org