Milkyway@home Separation CPU work not maxing out threads?

Author	Message
Chooka Send message Joined: 13 Dec 12 Posts: 101 Credit: 1,782,658,327 RAC: 0	Message 70144 - Posted: 11 Oct 2020, 8:06:19 UTC Last modified: 11 Oct 2020, 8:16:59 UTC So my 2 x 16 core processors (1950X & 3950X) are only crunching about 10, Milkyway@home Separation CPU wu/s at a time? I can't see why I don't have around 30 threads/ pc crunching cpu work whilst also crunching GPU work. Strangely, all my other pc's are maxing out the thread count which is what I'd expect. I am not talking about the n-body, mt work units in this question.This is specific to Milkyway@home Separation CPU wu/s What am I missing guys & girls? Edit - Yes, I know its not really worth crunching with the CPU, this was just a short test to see which is better, N-Body or Separation tasks on the CPU...but it's not much good if I can't max out my threads. ID: 70144 · Rating: 0 · rate: / Reply Quote

Chooka Send message Joined: 13 Dec 12 Posts: 101 Credit: 1,782,658,327 RAC: 0	Message 70145 - Posted: 11 Oct 2020, 9:54:23 UTC I'm still interested to know why all my threads weren't engaged but for the time being I've given up on the CPU crunching. I can't stand having threads idle. I could have run the N-Body tasks which are multithreaded but can I be bothered with the app config to divide my cores up? Not really. Not at the moment anyway. ID: 70145 · Rating: 0 · rate: / Reply Quote