logoalt Hacker News

simonask • today at 1:55 PM • 2 replies • view on HN

I hate this. We have a whole operating system doing its absolute best to prioritize hardware resources. Don't be out here throttling yourself.

Especially for something like compiling shaders. It literally never happens unless the user is about to go play a game, which is going to consume most resources anyway. To the user, there's nothing more important running right now.


Replies

cowlevel • today at 3:17 PM

Especially on Linux, the default throttling just doesn't work very well.

embedding-shape • today at 2:00 PM

> To the user, there's nothing more important running right now.

Well, to a certain degree. I have a relatively uncommon GPU, and run games on Steam (and Linux), so literally every game does shader compilation for me. Even with a beefy CPU and beefy GPU, if the shader compilation uses more than 16 threads, my computer basically freezes until its done with it, as it's so performance intensive, kind of have to throttle things if I want to be able to use the desktop for the 10 minutes the shader compilation takes sometimes.

Edit: "Do you use Linux? That only happened to me when I was using a dram-less ssd for swap and doing IO heavy operations on the NFS mounted drive"

I do! I do have NFS drives, but not for Steam games or anything else relevant. I'm also not using swap at all. RAM seems fine during this, it's just pegging all cores to 100% usage immediately and stays there, making everything else suffer.

➕ show 3 replies