vladstamate wrote:Hi Harun,
Thanks for the update. Good news then!
And yes, setting back the NumberThreads to 1 should make it behave properly. It is my fault that I left that setting there.
Thanks again for the testing and giving me feedback!
Regards,
Vlad.
Well, you might be right!
Just tested 022 on Arena 201:
When I set NumberThreads to 8 on a quad, I observe 100% cpu load.
When I set NumberThreads to 4 on a quad, I observe 100% cpu load
when calculating a new move and 75% cpu load after executing the move.
When I set NumberThreads to 2 on a quad, I observe 50% cpu load
when calculating a new move and 25% cpu load after executing the move.
When I set NumberThreads to 1 on a quad, I observe 25% cpu load
when calculating a new move and 0% cpu load after executing the move.
Interesting but may I conclude that plisk 022 does not ponder?!
Best,
I recall that Sloppy has some similarity.
It has an option of NumberThreads but it uses always 1cpu.
As far as I understand this multicore business is no easy thing.