home.social

#sysprof — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #sysprof, aggregated by home.social.

  1. For a long time I've been intrigued by #Epiphany taking 3 to 20 seconds to load most websites on startup or in Incognito Mode.

    Today I tested a bunch of configurations to report a bug, profiled… and it turned out to be 2 bugs in 1 :blobsweats:

    * The adblocker (and similar features) makes things slower :psyduck: : gitlab.gnome.org/GNOME/epiphan

    * WebKitGTK is doing some shenanigans with the system's fonts: bugs.webkit.org/show_bug.cgi?i

    #GNOMEWeb #WebKitGTK #GNOME #Sysprof #profiling #performance #Linux

  2. For a long time I've been intrigued by #Epiphany taking 3 to 20 seconds to load most websites on startup or in Incognito Mode.

    Today I tested a bunch of configurations to report a bug, profiled… and it turned out to be 2 bugs in 1 :blobsweats:

    * The adblocker (and similar features) makes things slower :psyduck: : gitlab.gnome.org/GNOME/epiphan

    * WebKitGTK is doing some shenanigans with the system's fonts: bugs.webkit.org/show_bug.cgi?i

    #GNOMEWeb #WebKitGTK #GNOME #Sysprof #profiling #performance #Linux

  3. For a long time I've been intrigued by #Epiphany taking 3 to 20 seconds to load most websites on startup or in Incognito Mode.

    Today I tested a bunch of configurations to report a bug, profiled… and it turned out to be 2 bugs in 1 :blobsweats:

    * The adblocker (and similar features) makes things slower :psyduck: : gitlab.gnome.org/GNOME/epiphan

    * WebKitGTK is doing some shenanigans with the system's fonts: bugs.webkit.org/show_bug.cgi?i

    #GNOMEWeb #WebKitGTK #GNOME #Sysprof #profiling #performance #Linux

  4. For a long time I've been intrigued by #Epiphany taking 3 to 20 seconds to load most websites on startup or in Incognito Mode.

    Today I tested a bunch of configurations to report a bug, profiled… and it turned out to be 2 bugs in 1 :blobsweats:

    * The adblocker (and similar features) makes things slower :psyduck: : gitlab.gnome.org/GNOME/epiphan

    * WebKitGTK is doing some shenanigans with the system's fonts: bugs.webkit.org/show_bug.cgi?i

    #GNOMEWeb #WebKitGTK #GNOME #Sysprof #profiling #performance #Linux

  5. For a long time I've been intrigued by #Epiphany taking 3 to 20 seconds to load most websites on startup or in Incognito Mode.

    Today I tested a bunch of configurations to report a bug, profiled… and it turned out to be 2 bugs in 1 :blobsweats:

    * The adblocker (and similar features) makes things slower :psyduck: : gitlab.gnome.org/GNOME/epiphan

    * WebKitGTK is doing some shenanigans with the system's fonts: bugs.webkit.org/show_bug.cgi?i

    #GNOMEWeb #WebKitGTK #GNOME #Sysprof #profiling #performance #Linux

  6. Stumbled upon another good example of a simple WordPress website theme causing scrolling performance problems in the latest version of GNOME Web (Epiphany), so I profiled the heck out of it with about 3.6 gigabytes of @WebKitGTK debug symbols installed: bugs.webkit.org/show_bug.cgi?i

    #QA #Sysprof #performance #profiling #GNOMEWeb #Epiphany #GNOME #WebKitGTK #WebKit

  7. Stumbled upon another good example of a simple WordPress website theme causing scrolling performance problems in the latest version of GNOME Web (Epiphany), so I profiled the heck out of it with about 3.6 gigabytes of @WebKitGTK debug symbols installed: bugs.webkit.org/show_bug.cgi?i

    #QA #Sysprof #performance #profiling #GNOMEWeb #Epiphany #GNOME #WebKitGTK #WebKit

  8. Stumbled upon another good example of a simple WordPress website theme causing scrolling performance problems in the latest version of GNOME Web (Epiphany), so I profiled the heck out of it with about 3.6 gigabytes of @WebKitGTK debug symbols installed: bugs.webkit.org/show_bug.cgi?i

    #QA #Sysprof #performance #profiling #GNOMEWeb #Epiphany #GNOME #WebKitGTK #WebKit

  9. Stumbled upon another good example of a simple WordPress website theme causing scrolling performance problems in the latest version of GNOME Web (Epiphany), so I profiled the heck out of it with about 3.6 gigabytes of @WebKitGTK debug symbols installed: bugs.webkit.org/show_bug.cgi?i

    #QA #Sysprof #performance #profiling #GNOMEWeb #Epiphany #GNOME #WebKitGTK #WebKit

  10. Stumbled upon another good example of a simple WordPress website theme causing scrolling performance problems in the latest version of GNOME Web (Epiphany), so I profiled the heck out of it with about 3.6 gigabytes of @WebKitGTK debug symbols installed: bugs.webkit.org/show_bug.cgi?i

    #QA #Sysprof #performance #profiling #GNOMEWeb #Epiphany #GNOME #WebKitGTK #WebKit

  11. Reported a new performance issue in Firefox's vertical tabs: resizing the width of that sidebar is extremely laggy, no matter the amount of tabs: bugzilla.mozilla.org/show_bug.

    Thankfully, I was able to use Sysprof for this, because Firefox's built-in profiler crashes.

    #Firefox #Sysprof #performance #profiling #Linux

  12. Reported a new performance issue in Firefox's vertical tabs: resizing the width of that sidebar is extremely laggy, no matter the amount of tabs: bugzilla.mozilla.org/show_bug.

    Thankfully, I was able to use Sysprof for this, because Firefox's built-in profiler crashes.

    #Firefox #Sysprof #performance #profiling #Linux

  13. Reported a new performance issue in Firefox's vertical tabs: resizing the width of that sidebar is extremely laggy, no matter the amount of tabs: bugzilla.mozilla.org/show_bug.

    Thankfully, I was able to use Sysprof for this, because Firefox's built-in profiler crashes.

    #Firefox #Sysprof #performance #profiling #Linux

  14. Reported a new performance issue in Firefox's vertical tabs: resizing the width of that sidebar is extremely laggy, no matter the amount of tabs: bugzilla.mozilla.org/show_bug.

    Thankfully, I was able to use Sysprof for this, because Firefox's built-in profiler crashes.

    #Firefox #Sysprof #performance #profiling #Linux

  15. Reported a new performance issue in Firefox's vertical tabs: resizing the width of that sidebar is extremely laggy, no matter the amount of tabs: bugzilla.mozilla.org/show_bug.

    Thankfully, I was able to use Sysprof for this, because Firefox's built-in profiler crashes.

    #Firefox #Sysprof #performance #profiling #Linux

  16. I stumbled upon a 2300-pages-long PDF document that actually is a fantastic benchmark for slow search performance (1.5 to 5 minutes) in most PDF readers (including GNOME Papers, Evince and Okular)… so I fired up #Sysprof through GNOME Builder to measure the slowness, and reported my findings in #Poppler for all of you performance optimization aficionados: gitlab.freedesktop.org/poppler

    #PDF #profiling #performance #FreeDesktop #Linux #GNOMEBuilder #GNOME #GNOMEPapers #Evince #Okular

  17. I stumbled upon a 2300-pages-long PDF document that actually is a fantastic benchmark for slow search performance (1.5 to 5 minutes) in most PDF readers (including GNOME Papers, Evince and Okular)… so I fired up #Sysprof through GNOME Builder to measure the slowness, and reported my findings in #Poppler for all of you performance optimization aficionados: gitlab.freedesktop.org/poppler

    #PDF #profiling #performance #FreeDesktop #Linux #GNOMEBuilder #GNOME #GNOMEPapers #Evince #Okular

  18. I stumbled upon a 2300-pages-long PDF document that actually is a fantastic benchmark for slow search performance (1.5 to 5 minutes) in most PDF readers (including GNOME Papers, Evince and Okular)… so I fired up #Sysprof through GNOME Builder to measure the slowness, and reported my findings in #Poppler for all of you performance optimization aficionados: gitlab.freedesktop.org/poppler

    #PDF #profiling #performance #FreeDesktop #Linux #GNOMEBuilder #GNOME #GNOMEPapers #Evince #Okular

  19. I stumbled upon a 2300-pages-long PDF document that actually is a fantastic benchmark for slow search performance (1.5 to 5 minutes) in most PDF readers (including GNOME Papers, Evince and Okular)… so I fired up #Sysprof through GNOME Builder to measure the slowness, and reported my findings in #Poppler for all of you performance optimization aficionados: gitlab.freedesktop.org/poppler

    #PDF #profiling #performance #FreeDesktop #Linux #GNOMEBuilder #GNOME #GNOMEPapers #Evince #Okular

  20. I stumbled upon a 2300-pages-long PDF document that actually is a fantastic benchmark for slow search performance (1.5 to 5 minutes) in most PDF readers (including GNOME Papers, Evince and Okular)… so I fired up #Sysprof through GNOME Builder to measure the slowness, and reported my findings in #Poppler for all of you performance optimization aficionados: gitlab.freedesktop.org/poppler

    #PDF #profiling #performance #FreeDesktop #Linux #GNOMEBuilder #GNOME #GNOMEPapers #Evince #Okular

  21. Discovered today that Epiphany (and presumably any application using #WebKitGTK) will experience slow scrolling after resizing the webview (or window) on some websites, particularly when you drag the scrollbar using the mouse (instead of using the scrollwheel), as can be seen in the video below.

    I have reported it here: bugs.webkit.org/show_bug.cgi?i

    Wondering if anyone experiences this on web pages other than this article: thewalrus.ca/return-to-office-

    #GNOMEWeb #GNOME #Sysprof #performance #profiling

  22. Discovered today that Epiphany (and presumably any application using #WebKitGTK) will experience slow scrolling after resizing the webview (or window) on some websites, particularly when you drag the scrollbar using the mouse (instead of using the scrollwheel), as can be seen in the video below.

    I have reported it here: bugs.webkit.org/show_bug.cgi?i

    Wondering if anyone experiences this on web pages other than this article: thewalrus.ca/return-to-office-

    #GNOMEWeb #GNOME #Sysprof #performance #profiling

  23. Discovered today that Epiphany (and presumably any application using #WebKitGTK) will experience slow scrolling after resizing the webview (or window) on some websites, particularly when you drag the scrollbar using the mouse (instead of using the scrollwheel), as can be seen in the video below.

    I have reported it here: bugs.webkit.org/show_bug.cgi?i

    Wondering if anyone experiences this on web pages other than this article: thewalrus.ca/return-to-office-

    #GNOMEWeb #GNOME #Sysprof #performance #profiling

  24. Discovered today that Epiphany (and presumably any application using #WebKitGTK) will experience slow scrolling after resizing the webview (or window) on some websites, particularly when you drag the scrollbar using the mouse (instead of using the scrollwheel), as can be seen in the video below.

    I have reported it here: bugs.webkit.org/show_bug.cgi?i

    Wondering if anyone experiences this on web pages other than this article: thewalrus.ca/return-to-office-

    #GNOMEWeb #GNOME #Sysprof #performance #profiling

  25. Discovered today that Epiphany (and presumably any application using #WebKitGTK) will experience slow scrolling after resizing the webview (or window) on some websites, particularly when you drag the scrollbar using the mouse (instead of using the scrollwheel), as can be seen in the video below.

    I have reported it here: bugs.webkit.org/show_bug.cgi?i

    Wondering if anyone experiences this on web pages other than this article: thewalrus.ca/return-to-office-

    #GNOMEWeb #GNOME #Sysprof #performance #profiling

  26. A performance testing surprise I did not have on my bingo card this month: #gitg being 3 times slower to reload a git repository compared to the initial load. It… it can't be! :blobsweats:

    gitlab.gnome.org/GNOME/gitg/-/

    #Sysprof #profiling #git #GNOME

  27. A performance testing surprise I did not have on my bingo card this month: #gitg being 3 times slower to reload a git repository compared to the initial load. It… it can't be! :blobsweats:

    gitlab.gnome.org/GNOME/gitg/-/

    #Sysprof #profiling #git #GNOME

  28. A performance testing surprise I did not have on my bingo card this month: #gitg being 3 times slower to reload a git repository compared to the initial load. It… it can't be! :blobsweats:

    gitlab.gnome.org/GNOME/gitg/-/

    #Sysprof #profiling #git #GNOME

  29. A performance testing surprise I did not have on my bingo card this month: #gitg being 3 times slower to reload a git repository compared to the initial load. It… it can't be! :blobsweats:

    gitlab.gnome.org/GNOME/gitg/-/

    #Sysprof #profiling #git #GNOME

  30. A performance testing surprise I did not have on my bingo card this month: #gitg being 3 times slower to reload a git repository compared to the initial load. It… it can't be! :blobsweats:

    gitlab.gnome.org/GNOME/gitg/-/

    #Sysprof #profiling #git #GNOME

  31. 5 days ago, I encountered a "somewhat serious, but niche" performance bug in #Inkscape where it would lock up the whole application while eating the CPU for 10 minutes when ungrouping thousands of objects at once (hello, EPS-imported files with text!).

    I profiled it with #Sysprof and full debug symbols, and reported it here: gitlab.com/inkscape/inkscape/-

    I thought, "Eh, 3.6+2.1K open issues? We'll see when they get to it 🤷"…

    Well… Yesterday, one of the @inkscape devs just fixed it! Impressive :owi:

  32. 5 days ago, I encountered a "somewhat serious, but niche" performance bug in #Inkscape where it would lock up the whole application while eating the CPU for 10 minutes when ungrouping thousands of objects at once (hello, EPS-imported files with text!).

    I profiled it with #Sysprof and full debug symbols, and reported it here: gitlab.com/inkscape/inkscape/-

    I thought, "Eh, 3.6+2.1K open issues? We'll see when they get to it 🤷"…

    Well… Yesterday, one of the @inkscape devs just fixed it! Impressive :owi:

  33. 5 days ago, I encountered a "somewhat serious, but niche" performance bug in #Inkscape where it would lock up the whole application while eating the CPU for 10 minutes when ungrouping thousands of objects at once (hello, EPS-imported files with text!).

    I profiled it with #Sysprof and full debug symbols, and reported it here: gitlab.com/inkscape/inkscape/-

    I thought, "Eh, 3.6+2.1K open issues? We'll see when they get to it 🤷"…

    Well… Yesterday, one of the @inkscape devs just fixed it! Impressive :owi:

  34. 5 days ago, I encountered a "somewhat serious, but niche" performance bug in #Inkscape where it would lock up the whole application while eating the CPU for 10 minutes when ungrouping thousands of objects at once (hello, EPS-imported files with text!).

    I profiled it with #Sysprof and full debug symbols, and reported it here: gitlab.com/inkscape/inkscape/-

    I thought, "Eh, 3.6+2.1K open issues? We'll see when they get to it 🤷"…

    Well… Yesterday, one of the @inkscape devs just fixed it! Impressive :owi:

  35. 5 days ago, I encountered a "somewhat serious, but niche" performance bug in #Inkscape where it would lock up the whole application while eating the CPU for 10 minutes when ungrouping thousands of objects at once (hello, EPS-imported files with text!).

    I profiled it with #Sysprof and full debug symbols, and reported it here: gitlab.com/inkscape/inkscape/-

    I thought, "Eh, 3.6+2.1K open issues? We'll see when they get to it 🤷"…

    Well… Yesterday, one of the @inkscape devs just fixed it! Impressive :owi:

  36. @clemej Better than "top" would be to install all debuginfo packages and measure with #Sysprof, maybe there is a performance bug that can be reported and solved there. See this guide: fedoramagazine.org/performance

  37. @clemej Better than "top" would be to install all debuginfo packages and measure with #Sysprof, maybe there is a performance bug that can be reported and solved there. See this guide: fedoramagazine.org/performance

  38. @clemej Better than "top" would be to install all debuginfo packages and measure with #Sysprof, maybe there is a performance bug that can be reported and solved there. See this guide: fedoramagazine.org/performance

  39. @clemej Better than "top" would be to install all debuginfo packages and measure with #Sysprof, maybe there is a performance bug that can be reported and solved there. See this guide: fedoramagazine.org/performance

  40. @clemej Better than "top" would be to install all debuginfo packages and measure with #Sysprof, maybe there is a performance bug that can be reported and solved there. See this guide: fedoramagazine.org/performance

  41. HiDPI in #GNOME is a great way to easily spot interesting performance issues.

    I tried out #GNOMEConnections to #RDP to a laptop that has a 4K display, and discovered that it's extremely slow compared to #Remmina connecting to that same machine:

    * High CPU usage when the window is focused and idle (no mouse cursors moving, no animations)
    * The client-moved cursor lags on the remote host
    * Moving windows lags a lot

    Reported as:
    * gitlab.gnome.org/GNOME/gnome-c
    * gitlab.gnome.org/GNOME/gnome-c

    #Sysprof

  42. HiDPI in #GNOME is a great way to easily spot interesting performance issues.

    I tried out #GNOMEConnections to #RDP to a laptop that has a 4K display, and discovered that it's extremely slow compared to #Remmina connecting to that same machine:

    * High CPU usage when the window is focused and idle (no mouse cursors moving, no animations)
    * The client-moved cursor lags on the remote host
    * Moving windows lags a lot

    Reported as:
    * gitlab.gnome.org/GNOME/gnome-c
    * gitlab.gnome.org/GNOME/gnome-c

    #Sysprof

  43. HiDPI in #GNOME is a great way to easily spot interesting performance issues.

    I tried out #GNOMEConnections to #RDP to a laptop that has a 4K display, and discovered that it's extremely slow compared to #Remmina connecting to that same machine:

    * High CPU usage when the window is focused and idle (no mouse cursors moving, no animations)
    * The client-moved cursor lags on the remote host
    * Moving windows lags a lot

    Reported as:
    * gitlab.gnome.org/GNOME/gnome-c
    * gitlab.gnome.org/GNOME/gnome-c

    #Sysprof

  44. HiDPI in #GNOME is a great way to easily spot interesting performance issues.

    I tried out #GNOMEConnections to #RDP to a laptop that has a 4K display, and discovered that it's extremely slow compared to #Remmina connecting to that same machine:

    * High CPU usage when the window is focused and idle (no mouse cursors moving, no animations)
    * The client-moved cursor lags on the remote host
    * Moving windows lags a lot

    Reported as:
    * gitlab.gnome.org/GNOME/gnome-c
    * gitlab.gnome.org/GNOME/gnome-c

    #Sysprof

  45. HiDPI in #GNOME is a great way to easily spot interesting performance issues.

    I tried out #GNOMEConnections to #RDP to a laptop that has a 4K display, and discovered that it's extremely slow compared to #Remmina connecting to that same machine:

    * High CPU usage when the window is focused and idle (no mouse cursors moving, no animations)
    * The client-moved cursor lags on the remote host
    * Moving windows lags a lot

    Reported as:
    * gitlab.gnome.org/GNOME/gnome-c
    * gitlab.gnome.org/GNOME/gnome-c

    #Sysprof

  46. maybe someone is interested:

    I was compiling gnome-inform just copy and pasting the instructions by @ptomato

    this just works

    github.com/ptomato/inform7-ide

    at the end i have a working build of a fresh inform7-ide. and with my most famous bug:
    inform7.atlassian.net/browse/I

    is anyone good in using #sysprof ?

    to use it just with the terminal i use this command:

    ./inform7/Tangled/inform7 -project "~/adventure.inform/" -format "Inform6/16" && ./inform6/Tangled/inform6 -E2w~SDG ~/adventure.inform/Build/auto.inf -o ~/adventure.inform/Build/adventure-built.ulx

    it takes the inform7 source text, compiles it to inform6, creates the .ulx file, which you can "play" using glulx.

    and yes, i would like to have that bug fixed ;)

    #inform7 #terminal #vacation

  47. maybe someone is interested:

    I was compiling gnome-inform just copy and pasting the instructions by @ptomato

    this just works

    github.com/ptomato/inform7-ide

    at the end i have a working build of a fresh inform7-ide. and with my most famous bug:
    inform7.atlassian.net/browse/I

    is anyone good in using #sysprof ?

    to use it just with the terminal i use this command:

    ./inform7/Tangled/inform7 -project "~/adventure.inform/" -format "Inform6/16" && ./inform6/Tangled/inform6 -E2w~SDG ~/adventure.inform/Build/auto.inf -o ~/adventure.inform/Build/adventure-built.ulx

    it takes the inform7 source text, compiles it to inform6, creates the .ulx file, which you can "play" using glulx.

    and yes, i would like to have that bug fixed ;)

    #inform7 #terminal #vacation

  48. maybe someone is interested:

    I was compiling gnome-inform just copy and pasting the instructions by @ptomato

    this just works

    github.com/ptomato/inform7-ide

    at the end i have a working build of a fresh inform7-ide. and with my most famous bug:
    inform7.atlassian.net/browse/I

    is anyone good in using #sysprof ?

    to use it just with the terminal i use this command:

    ./inform7/Tangled/inform7 -project "~/adventure.inform/" -format "Inform6/16" && ./inform6/Tangled/inform6 -E2w~SDG ~/adventure.inform/Build/auto.inf -o ~/adventure.inform/Build/adventure-built.ulx

    it takes the inform7 source text, compiles it to inform6, creates the .ulx file, which you can "play" using glulx.

    and yes, i would like to have that bug fixed ;)

    #inform7 #terminal #vacation

  49. maybe someone is interested:

    I was compiling gnome-inform just copy and pasting the instructions by @ptomato

    this just works

    github.com/ptomato/inform7-ide

    at the end i have a working build of a fresh inform7-ide. and with my most famous bug:
    inform7.atlassian.net/browse/I

    is anyone good in using #sysprof ?

    to use it just with the terminal i use this command:

    ./inform7/Tangled/inform7 -project "~/adventure.inform/" -format "Inform6/16" && ./inform6/Tangled/inform6 -E2w~SDG ~/adventure.inform/Build/auto.inf -o ~/adventure.inform/Build/adventure-built.ulx

    it takes the inform7 source text, compiles it to inform6, creates the .ulx file, which you can "play" using glulx.

    and yes, i would like to have that bug fixed ;)

    #inform7 #terminal #vacation

  50. maybe someone is interested:

    I was compiling gnome-inform just copy and pasting the instructions by @ptomato

    this just works

    github.com/ptomato/inform7-ide

    at the end i have a working build of a fresh inform7-ide. and with my most famous bug:
    inform7.atlassian.net/browse/I

    is anyone good in using #sysprof ?

    to use it just with the terminal i use this command:

    ./inform7/Tangled/inform7 -project "~/adventure.inform/" -format "Inform6/16" && ./inform6/Tangled/inform6 -E2w~SDG ~/adventure.inform/Build/auto.inf -o ~/adventure.inform/Build/adventure-built.ulx

    it takes the inform7 source text, compiles it to inform6, creates the .ulx file, which you can "play" using glulx.

    and yes, i would like to have that bug fixed ;)

    #inform7 #terminal #vacation