Technology

58151 readers

3878 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago

MODERATORS

[email protected]

497

Firefox Got Faster for Real Users in 2023 (hacks.mozilla.org)

submitted 10 months ago by [email protected] to c/[email protected]

44 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 10 months ago* (last edited 10 months ago) (1 children)

Nope, Debian Testing on machine with 12 cores and 32GB of RAM and 3GB/s M.2 drive.

And my systemd-analyze says graphical.target reached after 5.690s in userspace. Most of which is network manager waiting for online status, mounting filesystems, and timesyncd waiting clock update.

[–] [email protected] 3 points 10 months ago (1 children)

Sounds like you have a borked dbus or is using the GTK_USE_PORTAL env variable, 20 second timeouts are gtks standard way of dealing with something it doesn't like. Firefox should take < 1 second to start fresh and takes < 3s for me, restoring hundreds of tabs

[–] [email protected] 1 points 10 months ago

Hm, interesting idea. Any suggestion how I can check/reset this?