[Webkit-unassigned] [Bug 279026] REGRESSION(281488 at main?): Process launching is slow under flatpak

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=279026

Michael Catanzaro <mcatanzaro at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mcatanzaro at redhat.com

--- Comment #1 from Michael Catanzaro <mcatanzaro at redhat.com> ---
At great difficulty, I built a custom flatpak with some extra debug code to time how long we spend in IPC::readPIDFromPeer (in ConnectionUnix.cpp). With 14 tabs, it looks like this:

Read pid from peer in 33 milliseconds
Read pid from peer in 152 milliseconds

(epiphany:2): Gtk-WARNING **: 14:15:57.155: Unable to retrieve the Flatpak portal version: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown
Read pid from peer in 152 milliseconds
Read pid from peer in 143 milliseconds
Read pid from peer in 149 milliseconds
Read pid from peer in 148 milliseconds
Read pid from peer in 143 milliseconds
Read pid from peer in 141 milliseconds
Read pid from peer in 136 milliseconds
Read pid from peer in 143 milliseconds
Read pid from peer in 140 milliseconds
Read pid from peer in 143 milliseconds
Read pid from peer in 142 milliseconds
Read pid from peer in 149 milliseconds
Read pid from peer in 148 milliseconds

I think the first process is quicker to spawn because it's the unsandboxed network process rather than the sandboxed web process.

I repeated the test in my normal development environment, without flatpak:

Read pid from peer in 21 milliseconds
Read pid from peer in 40 milliseconds
Read pid from peer in 41 milliseconds
Read pid from peer in 43 milliseconds
Read pid from peer in 43 milliseconds
Read pid from peer in 43 milliseconds
Read pid from peer in 43 milliseconds
Read pid from peer in 43 milliseconds
Read pid from peer in 42 milliseconds
Read pid from peer in 43 milliseconds
Read pid from peer in 42 milliseconds
Read pid from peer in 43 milliseconds
Read pid from peer in 42 milliseconds
Read pid from peer in 41 milliseconds
Read pid from peer in 41 milliseconds

So flatpak makes things much worse, but I'd say performance is unacceptable in both cases.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20240906/14caab4b/attachment-0001.htm>