Joost't wrote:
> Yes, I posted about these stockfish anomalies before.
>
> And have some ideas in handling this; although I also hope that next sf
> releases will somehow start to behave...
Stockfish 191 was very bad. I just upgraded to 2.0.1 and it seems better
behaved.
The way it loads up the CPU makes me wonder it's not hindering it's
opponents in some sly manner when playing computer tournaments
running on the one host.
> > Do you know which is the bottleneck?
> > formatPV maybe?
> But: The fact that the receiving scid-end of the communication channel
> with the engine is implemented in tcl is certainly a big issue.
Yah... you're right. But moving all the pipe handling and input parsing from
tcl
to C
is a big issue and not worth the effort imho considering the super-powered
nature of modern CPUs.
Steve
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Scid-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/scid-users
