>I'm not familiar with the Firefox codebase...sound like a good project for a motivated student to work on during GSoC...blasting in with no actual code...I see no real attempts at developing an actual software solution https://bugzilla.mozilla.org/show_bug.cgi?id=1532955 which had to be disabled because of https://bugzilla.mozilla.org/show_bug.cgi?id=1780058 See also https://bugzilla.mozilla.org/show_bug.cgi?id=1532955#c14 and the follow-ups there for other suggestions that don't actually work well.
Bug 1755038 Comment 13 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
>I'm not familiar with the Firefox codebase...sound like a good project for a motivated student to work on during GSoC...blasting in with no actual code...I see no real attempts at developing an actual software solution https://bugzilla.mozilla.org/show_bug.cgi?id=1532955 which had to be disabled because of https://bugzilla.mozilla.org/show_bug.cgi?id=1780058 See also https://bugzilla.mozilla.org/show_bug.cgi?id=1532955#c14 and the follow-ups there for other suggestions that don't actually work well. The real problem is that if this kind of detection misfires, it will crater performance too.
>I'm not familiar with the Firefox codebase...sound like a good project for a motivated student to work on during GSoC...blasting in with no actual code...I see no real attempts at developing an actual software solution https://bugzilla.mozilla.org/show_bug.cgi?id=1532955 which had to be disabled because of https://bugzilla.mozilla.org/show_bug.cgi?id=1780058 See also https://bugzilla.mozilla.org/show_bug.cgi?id=1532955#c14 and the follow-ups there for other suggestions that don't actually work well. The real problem is that if this kind of detection misfires, it will crater performance too, and it's not trivial to measure whether any of these measures improve the user experience and make it worse (overall, let alone for outliers).
>I'm not familiar with the Firefox codebase...sound like a good project for a motivated student to work on during GSoC...blasting in with no actual code...I see no real attempts at developing an actual software solution https://bugzilla.mozilla.org/show_bug.cgi?id=1532955 which had to be disabled because of https://bugzilla.mozilla.org/show_bug.cgi?id=1780058 See also https://bugzilla.mozilla.org/show_bug.cgi?id=1532955#c14 and the follow-ups there for other suggestions that don't actually work well. The real problem is that if this kind of detection misfires, it will crater performance too, and it's not trivial to measure whether any of these measures improve the user experience and make it worse (overall, let alone for outliers), because dropping caches or unloading pages at the wrong time also worsen the user experience just as much as being slow does.
>I'm not familiar with the Firefox codebase...sound like a good project for a motivated student to work on during GSoC...blasting in with no actual code...I see no real attempts at developing an actual software solution https://bugzilla.mozilla.org/show_bug.cgi?id=1532955 which had to be disabled because of https://bugzilla.mozilla.org/show_bug.cgi?id=1780058 See also https://bugzilla.mozilla.org/show_bug.cgi?id=1532955#c14 and the follow-ups there for other suggestions that don't actually work well. The real problem is that if this kind of detection misfires, it will crater performance too, and it's not trivial to measure whether any of these measures improve the user experience and make it worse (overall, let alone for outliers), because dropping caches or unloading pages at the wrong time also worsens the user experience just as much as being slow does.
>I'm not familiar with the Firefox codebase...sound like a good project for a motivated student to work on during GSoC...blasting in with no actual code...I see no real attempts at developing an actual software solution https://bugzilla.mozilla.org/show_bug.cgi?id=1532955 which had to be disabled because of https://bugzilla.mozilla.org/show_bug.cgi?id=1780058 See also https://bugzilla.mozilla.org/show_bug.cgi?id=1532955#c14 and the follow-ups there for other suggestions that don't actually work well. The real problem is that if this kind of detection misfires, it will crater performance too, and it's not trivial to measure whether any of these measures improve the user experience and make it worse (overall, let alone for outliers), because dropping caches or unloading pages at the wrong time also worsens the user experience just as much as being slow does. Combine this with Linux being quite diverse with ZFS, etc having different ideas about memory allocation, systemd scopes, etc, and there's ample opportunity to go wrong.
>I'm not familiar with the Firefox codebase...sound like a good project for a motivated student to work on during GSoC...blasting in with no actual code...I see no real attempts at developing an actual software solution https://bugzilla.mozilla.org/show_bug.cgi?id=1532955 which had to be disabled because of (at the very least) https://bugzilla.mozilla.org/show_bug.cgi?id=1780058 See also https://bugzilla.mozilla.org/show_bug.cgi?id=1532955#c14 and the follow-ups there for other suggestions that don't actually work well. The real problem is that if this kind of detection misfires, it will crater performance too, and it's not trivial to measure whether any of these measures improve the user experience and make it worse (overall, let alone for outliers), because dropping caches or unloading pages at the wrong time also worsens the user experience just as much as being slow does. Combine this with Linux being quite diverse with ZFS, etc having different ideas about memory allocation, systemd scopes, etc, and there's ample opportunity to go wrong.