29,90 €
When you analyse with an engine do you understand all the data in the engine window? Fritz calculates with 2317 kN/sec and a cloud engine with 121 MN/sec?
This has to do with the speed and the performance of the engine. But what exactly are nodes?
The engine window shows us how many nodes per second the engine calculates.
Schematically, the search for positions or moves can be shown as a kind of tree with various branches (that is why we talk about "opening tree" or "search tree"). However, transpositions lead to the same position but via different routes and the repetition of moves may create loops — therefore one talks about nodes. A node is the whole of a position including its history (e.g. castling or a repetition of moves) and its evaluation. Some engines operate with "thin" nodes — that is little evaluation — and are therefore very fast.
Other engines operate with "thick" nodes — a lot of evaluation — and are slower. Therefore, it does not say much if you compare the number of nodes various engines calculate directly!
The speed with which positions are analysed is given in "nodes per second" (n/sec), and to avoid having to deal with huge numbers you give the numbers as kN/s (thousand nodes/sec) or MN/s (million nodes/sec). You can see the speed of the analysis or the number of positions analysed.
If you click on the engine view that indicates the calculation speed you can choose to see nodes/sec or to see the total number of nodes the engine has calculated.
But be careful: if you want to compare computer performances you can only use these technical data (nodes per second, search depth) if you test the computers with the same engines.
By the way: there are positions the engine does not have to calculate, e.g. endgames in the endgame database (if the engine has access to these databases) or positions in the opening book.
Back to List
to send a comment please fill the form:
Name *
Email Address *
Subject
Feedback *
