3 ms·
Oh cool! So, does that update this file, too, so it always does it this way? Or? I'm definitely not familiar with the tricks they're doing here. Looks like an
by t-writescode 5y ago
Oh cool! So, does that update this file, too, so it always does it this way? Or?
I'm definitely not familiar with the tricks they're doing here. Looks like an ini file!
- throwaway09223 5y agoIt's: taskset <arguments> <command to run> So to run `ls ~` on only cpu0 you would run: taskset -c 0 ls ~ Run it each time you want to invoke the command.
- t-writescode 5y agoIt seems like the article itself updates the icon on the desktop to always use those specific processors, though, right?
- serf 5y agothat's true -- but given that not all desktop environments respect the idea of *.desktop , and not all distributions use /.local/share, so , pedantically, the parent that suggests 'taskset -c 0-4 ZoomLauncher' suggests a tip that will work on just about every linux distribution, however the git snippet that was linked as the parent of this thread will only work on a handful of distribution/desktop-environment combinations. tl;dr : parent to your comment suggests a more generalized 'for linux' solution that doesn't depend on specific flavor nuances and desktop environs. (user 10000truths has a good point, it sets memory ceilings as well -- this should still be done in a way that is distro-agnostic.)