Originally Posted by Finrond
So a month or two back I got a new server for work (2P E5 2640 v3). While I waited for hard drives and memory, I slapped a crappy hard drive in it and installed Server 2016 preview on it. Of course the first thing I installed was BOINC. I've noticed some interesting behavior with some of the projects and I believe it to be OS related.
Sometimes I will check on it to see how it's doing and all the work is being done on one CPU group (CPU1 or CPU2), so all 32 threads will be crunching on only one of the cpus. When I manually go in and change the affinity on half of them, everything works fine until those units complete and then it reverts back to only running on one CPU. I think it is because server 2016 sees it as one application, and you can only assign it to one cpu group for some reason:
Perhaps this is just a bug or something with the Technical Preview, but I would stay away from server 2016 for crunching for now.
Does the windows task manager affinity settings persist once that particular copy of the exe closes? I don't think it does in Win7 and I think thats why I went with Process Lasso for folding as Process Lasso always kept the affinity for a particular exe name each time it opens. I wanted to keep the CPU threads on separate cores from the GPU exe. With task manager I thought I had them do rest once that WU completed and then the exe opened again with default affinity.
As to why they all jumped to 1 CPU instead of both that may be a separate issue.
I have a few Universe WUs stored up, not many though, on the 3570k and E66.