A program, after I tinkered with it, is using ALL 32 threads in low priority.

Makes the desktop WAY more responsive.

Wish I had a clue what in the hell you are talking about

Is your implication that the CPU isn't able to throttle quickly?

The program is supposed to run as a user process with normal priority( green in Htop are user processes, red are kernel and blue is low priority processes), I did something to it force it into running in low priority.

Low priority threads will be forced to give up cpu cycles when a higher priority thread needs them, so what I did was make the program run more like a background process even tho its not supposed to.

Normally when this program runs it make the desktop pretty damn sluggish, but now its pretty responsive running as a low priority since anything I do on the desktop like a browser or whatever other program I run takes priority with the cpu cycles with of course a hit in performance of the now low priority threaded program.

Its funny to me because its not supposed to do that at all and I accidentally the whole thing

Normally when that program runs all 32 threads I have to make a choice between running that program and not using that pc for anything else or just not running that program.

It's just cool in a computer nerdy kind of a way and a good thing I don't have Dr Evil tendencies.

Not at all, with the program now running in low priority its just the opposite.

So...your CPU is really fast at context switching?

Your uptime leaves a lot to be desired.  

It's a desktop that dual boots Windows 10.

Two versions of Win10, or Win 10 and <something else>?
(That terminal window makes me think some flavor of Linux.)

I will just say ... nice.

Ubuntu 17.04 as main os and Windows 10 on second hard drive.

Did you tinker with the program and forget nice/renice exist?

Nope, It is totally unrelated to nice/renice.

If I remember correctly with nice/renice you have to configure each thread, what I did was have a error in the config. file.

Original:

""cpu-affinity": null,"
""cpu-priority": null,"

The "cpu-affinity:" is where you can leave it "null" and the program uses the Linux scheduler to decide or you can edit it to " 0xAEAEAEAE" or "0xFFFFFFFF" for 8 threads, or however many you want or need, and to run on 8 threads on certain cores.

The "cpu-priority:' is to prioritize which cpu in multi-cpu systems or leave it "null" to let Linux decide.

I accidentally edited to this  ""cpu-priority": 0x,"

And that is what made it do what it did.

I'm not 100% sure but you may be mixing up threads and processes. But I understand what you are saying.

A process has  a PID and individually show up in top/ps. If you nice the parent process on startup then all the child processes inherit their priority in general.

A process can have multiple child threads. These don't show up in ps/top in most cases. But they can still chew up cpu cycles on multiple cores. If you have ever seen a single process using using more than 100% cpu in top, then it has multiple threads taxing the cpus.