Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
historians.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Historians.social is open to all who are interested in history.

Administered by:

Server stats:

231
active users

historians.social: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.4

#sysprof

1 post1 participant0 posts today
Jeff Fortin T.<p>Made some progress in investigating the likely cause of slowness for some <a href="https://mastodon.social/tags/GNOMECalendar" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GNOMECalendar</span></a> users who have a metric shitton of events to display: <a href="https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/1381#note_2375819" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">gitlab.gnome.org/GNOME/gnome-c</span><span class="invisible">alendar/-/issues/1381#note_2375819</span></a></p><p><a href="https://mastodon.social/tags/Sysprof" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Sysprof</span></a> <a href="https://mastodon.social/tags/performance" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>performance</span></a> <a href="https://mastodon.social/tags/GNOME" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GNOME</span></a></p>
Jeff Fortin T.<p>STOP DOING NEW <a href="https://mastodon.social/tags/HARDWARE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HARDWARE</span></a></p><p>* CPUs were not supposed to be idle<br>* YEARS OF NEXTGEN yet NO REAL-WORLD USE for going higher than SANDYBRIDGE<br>* Wanna go faster for a laugh? We've a tool for that: it's called <a href="https://mastodon.social/tags/SYSPROF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SYSPROF</span></a><br>"Please give me 192 CORES. Please give me INFINITY of BogoMips"—Statements dreamed up by datacenters</p><p>LOOK what Silicon Vendors have been demanding your respect for with all the chipsets we built for them<br>*Points at bunch of single-threaded software*</p><p>They've played us for absolute fools</p>
Jeff Fortin T.<p>New hardcore <a href="https://mastodon.social/tags/PDF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>PDF</span></a> rendering performance benchmark for <a href="https://mastodon.social/tags/Poppler" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Poppler</span></a>:<br>"Jesus Christ it's a <a href="https://mastodon.social/tags/Lyon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Lyon</span></a> (map), get in the car!" :blobnom:</p><p>That map takes 26 seconds to render with Poppler on <a href="https://mastodon.social/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Linux</span></a>, but only 6 seconds with PDFjs, or 15 seconds with XPDF: <a href="https://gitlab.freedesktop.org/poppler/poppler/-/issues/1555" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">gitlab.freedesktop.org/poppler</span><span class="invisible">/poppler/-/issues/1555</span></a></p><p>I've profiled the issue on the various Poppler rendering backends, and there are some hypotheses about the slowness. If anyone can help fix this, that would be fantastic.</p><p><a href="https://mastodon.social/tags/Okular" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Okular</span></a> <a href="https://mastodon.social/tags/GNOMEPapers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GNOMEPapers</span></a> <a href="https://mastodon.social/tags/Evince" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Evince</span></a> <a href="https://mastodon.social/tags/Sysprof" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Sysprof</span></a> <a href="https://mastodon.social/tags/profiling" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>profiling</span></a></p>
Jeff Fortin T.<p>Found out out why <a href="https://mastodon.social/tags/GNOME" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GNOME</span></a> System&nbsp;Monitor sometimes consumes suspicious amounts of CPU with peaks every now and then. Seems like it happens when the mouse hovers and/or moves across the processes list :blobsweats: <br><a href="https://gitlab.gnome.org/GNOME/gnome-system-monitor/-/issues/319" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">gitlab.gnome.org/GNOME/gnome-s</span><span class="invisible">ystem-monitor/-/issues/319</span></a></p><p>I don't know if what I found is GNOME System Monitor doing too much work for those tooltips, or if I found a performance bug in <a href="https://mastodon.social/tags/GTK" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GTK</span></a> itself. The <a href="https://mastodon.social/tags/Sysprof" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Sysprof</span></a> capture makes it look like it's doing something very expensive with GTK 🤔</p>
ExploreLive feeds
About