Remix.run Logo
▲ simonask 2 hours ago

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.

▲cowlevel an hour ago | parent | next [-]

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

▲embedding-shape 2 hours ago | parent | prev [-]

> 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.

▲Aurornis an hour ago | parent | next [-]

> 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

Strange. This never happens to me on Windows. I only notice that the fans spin up a little because all cores are pegged.

▲jack_pp an hour ago | parent [-]

i've only seen the shader compilation on linux.

▲braiamp 2 hours ago | parent | prev | next [-]

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, since the system will use ram as a buffer (which pushes things to swap)

▲Hendrikto 2 hours ago | parent | prev [-]

> Even with a beefy CPU and beefy GPU, if the shader compilation uses more than 16 threads, my computer basically freezes

Sounds like a scheduling problem that should be adressed at the OS level.

▲embedding-shape 2 hours ago | parent [-]

Seems a deep one if so. I've tried a bunch of alternative schedulers to try to avoid the issue, like Bore and BMQ, but seems to happen regardless. Been like this on previous computers too, fwiw, unless I turn down the concurrency for shader compilation stuff will lag heavily until it finishes.

▲bilegeek 2 hours ago | parent | next [-]

> tried a bunch of alternative schedulers

1. Have you tried enabling full preemption as well? I run Debian, and before I did that I had lots of stutters from any kind of background load thanks to dynamic preemption.

2. Even then, ZFS was causing stutters until I lowered it's priority as well (spl_taskq_thread_priority=0)

3. On non-ZFS drives, try setting your I/O scheduler to Kyber for NVME or BFQ for everything else. "mq-deadline" isn't great for interactive use on a SATA SSD, even for non-boot drives, and even NVME sometimes stutters under "none" for some people.

> I'm also not using swap at all.

4. zswap (combined with zstd compression, "min_ttl_ms=1000", and "vm.page-cluster=0") and "defer+madvise" memory compaction can help. (Something about the kernel really liking having swap on-hand.)

Steam runs shader compilations at batch policy and nice 19, so without RAM or I/O bottlnecks even gaming shouldn't be too bad (though from personal experience it still induces some stuttering). It's just most distros are tuned horribly for this. (Not to sound flippant, I understand the frustration of "just try this" and it doesn't work, but it's everything I can think of RN.)

▲jordanb 11 minutes ago | parent | prev [-]

You could try cpu pinning or ulimits to limit the program from using one core so there's always one free.

But it's also possible that the problem is in the kernel and the shaders are actually doing some system call that's locking up the kernel. Like maybe there's a bug in your cuda or nvidia driver that's causing the kernel to lock.