#Salad disables GPU if DSX (controller driver software) is running
44 messages · Page 1 of 1 (latest)
I also just learned Salad disables the GPU if OBS is running... never mind if I only have it open so I can see my capture card's output, as I'm playing a console to avoid disrupting Salad...
we love the workload blocklist 🔥 (sarcastic)
And yeah the reason why it's blocked is because salad has a "database" of apps and occasionally runs a check on what apps you have open and if it detects an app on the blocklist, there goes your GPU workloads
And it's stupid since all it does is base it off app name, not even the usage, what GPU it's running on, or if it's even compatible with salad
Someone else also had this, they were told to contact support and maybe it could be removed from the blocklist
Not sure tho
The help text implies it goes off of workload, but considering my GPU was doing NOTHING just now, it merely had OBS open... I believe you.
And yeah they unfortunately also block OBS which sucks as it doesn't even matter if it's using a seperate GPU to encode, salad only sees obs and blocks workloads
Yeah the blocklist is unfortunately just process based, which really sucks
What makes this worse is that it's persistent
It takes effect the moment you start salad with GPU enabled, so it still blocks GPU workloads of an app is running even if you don't have a container so you can't even do productive work lmao
though this app is meant to be ran afk tho
But even then it could take a while to get a container and the user can't do useful work
Salad literally blocks game launchers aswell lol, not even the actual game itself
Well, atleast the Minecraft launcher
But yeah, thank the people who abuse salad and game while running a container before this was implemented, they were probably the reason why salad added this stupid blocklist
Now we can't even run obs on integrated graphics or even without a video stream at all without salad blocking GPU workloads
The worst part is that you have to stop chopping and start again for it to lift
Just closing the offending program isn't enough
So for many hours Salad was saying it was running, but not actually doing anything
Yeah, unfortunately it's persistent throughout the whole chopping session, can't just close the offending app or re-enable GPU you have to completely stop salad and possibly kill off CPU containers/bandwidth sharing aswell
rip
There should be a lil stop sign or some other icon on the system tray icon if something's wrong IMO
Would be better if salad uses nvidia-smi to monitor GPU activity when a container is about to start and notify the user a container is coming then block GPU workloads if the user continues to do GPU heavy stuff
Way better than a predefined blocklist that takes account nothing other than app name
In fact, what's funnier is that salad does this to GPUs that aren't even compatible with containers aswell lol
So it even kills off mining workloads on my container-incompatible Intel arc GPU which makes no sense since mining isn't contributing to the salad network lmao
^kills off non-existent workloads on my integrated GPU on my laptop too lol
Oh right salad doesn't even go degraded when GPU workloads get blocked lol, just stays green. Only shows a very short overlay that can easily be missed if you're not looking
Which adds on to why Nvidia smi would be a better alternative, since it won't be blocking non Nvidia GPUs that can't even run containers^
Anyways enough yap 2:30am
Thank you for your insight
I've been a long-time workload blocklist hater lmao
from personal experience, I'm pretty sure this isn't actually the case
the insanely smart and talented devs just decided to not put a retry or dismiss button on the notification
I accidentally ran Minecraft for 0.0002 picoseconds and Salad "blocked workloads for this chopping session" with supposedly no way to retry without stopping and starting chopping.
Issue was that I was on a good bandwidth sharing earnings streak so it worked out better to keep Salad only running bandwidth sharing than hope for a $1.30 container that would've only lasted an hour or two anyways.
So after the offending application was ended, I disabled and re-enabled GPU usage. Turns out a day or two later (thanks to the shit demand back then) I got a GPU container.
Interesting
The degraded error message stuck around even after running multiple different containers. That was until I got a different error message that was retryable / dismissable, and it replaced the workloads blocked error message.
Is there a publicly-available blocklist that Salad uses or is it all obfuscated? I wanna know what random-ass program is going to set it off.
heres a list of all apps that salad blocks when you have it running https://app-api.salad.com/api/v2/intensive-processes (before mods kill me, this is public)
Unfortunately im not sure what salad uses to actually detect what apps you have open, id assume its tasklist or something similar (i do see it appear in my task manager every now and then) but I dont think they use the one in the system32 folder
ok yup im pretty sure salad uses tasklist, just saw it in task manager
Thanks!
That's incredible! Thanks for sharing the list.
yeah its great that salad made this public api so users can know what apps they cant run along with gpu containers