Post #1496609
2026-02-05 14:46 UTC
@pid_eins
best case: 6 context switches [request: app -> dbus-proxy -> broker -> portal frontend] -> [response: broker -> dbus-proxy -> app]
but with auth required on every connection: 8 context switches [request: app -> dbus-proxy -> broker -> portal frontend -> [credentials: broker -> portal frontend]] -> [response: broker -> dbus-proxy -> app]
and with a backend call: 12 context switches [request: app -> dbus-proxy -> broker -> portal frontend -> [credentials: broker -> portal frontend] -> broker -> portal backend] -> [response: broker -> portal frontend -> broker -> dbus-proxy -> app]
Replies (3)
-
@swick@hachyderm.io 2026-02-05 14:48
@pid_eins oh, and with varlink and appd it can be exactly two because no more dbus-proxy, no more frontend/backend split, and no call for the creds/permissions.
-
@pid_eins@mastodon.social 2026-02-05 15:06
@swick aaaaaah
-
@bugaevc@floss.social 2026-02-05 15:44
@swick @pid_eins you should multiply that by two, since you're switching into and out of kernel mode on every turn. Also GDBus that underlies this all does a bunch of thread hopping internally, so there's more switches still.