• 0 Posts
  • 8 Comments
Joined 3 months ago
Cake day: April 7th, 2024
  • scsitoLinux@programming.dev•Is there a way to keep Linux responsive when at ~100% CPU usage?
    601·
    8 days ago

    The Linux kernel uses the CPU default scheduler, CFS, a mode that tries to be fair to all processes at the same time - both foreground and background - for high throughput. Abstractly think “they never know what you intend to do” so it’s sort of middle of the road as a default - every CPU cycle of every process gets a fair tick of work unless they’ve been intentionally nice’d or whatnot. People who need realtime work (classic use is for audio engineers who need near-zero latency in their hardware inputs like a MIDI sequencer, but also embedded hardware uses realtime a lot) reconfigure their system(s) to that to that need; for desktop-priority users there are ways to alter the CFS scheduler to help maintain desktop responsiveness.

    Have a look to Github projects such as this one to learn how and what to tweak - not that you need to necessarily use this but it’s a good point to start understanding how the mojo works and what you can do even on your own with a few sysctl tweaks to get a better desktop experience while your rust code is compiling in the background. https://github.com/igo95862/cfs-zen-tweaks (in this project you’re looking at the set-cfs-zen-tweaks.sh file and what it’s tweaking in /proc so you can get hints on where you research goals should lead - most of these can be set with a sysctl)

    There’s a lot to learn about this so I hope this gets you started down the right path on searches for more information to get the exact solution/recipe which works for you.

  • scsitoMeta (lemm.ee)•Thumbnail Preview Links Broken?
    2·
    17 days ago

    It’s possible what you are seeing is more visible than before due to issue #2433 which is:

    When images are broken, a blank space is all that is shown. A fallback image for broken images would make this more apparent.

    With the 0.19.4 update I notice it a lot more now and see a lot from apnews.com causing this, on my Subscribed view with news@lemmy.world and world@lemmy.world (and others) this morning I count:

    Sites that are fine: www.cnbc.com, www.nbcnews.com, www.bbc.com, www.cbsnews.com, newrepublic.com and a bunch of fediverse instances and other “not mainstream” sites from around the internet. it would appear that whatever has changed in code is interacting badly with certain mainstream news sites and the ability to get a thumbnail - I browsed the lemmy-ui commits and a metric ton of 3rd party dependencies were updated, gave up looking for the cause.