What engines calculate

by ChessBase
3/5/2018 – Nodes, and lots of them! 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? Sure, this has to do with the speed and the performance of the engine but what exactly are nodes? | Photo: Nadja Wittmann (ChessBase)

Fritz 16 - He just wants to play! Fritz 16 - He just wants to play!

Fritz 16 is looking forward to playing with you, and you're certain to have a great deal of fun with him too. Tense games and even well-fought victories await you with "Easy play" and "Assisted analysis" modes.

More...

What's in a node?

What does the term "nodes" mean with respect to the calculation of variations? The engine window shows us how many nodes per second the engine calculates.

Engine

In our example, the engine calculates with a speed of 3,232,000 nodes per second

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.

Fritz also analyses in the replayer on ChessBase News — depending on the type of position with 1000 kN/s or up to 2500 kN/s — and clicking on the ventilator symbol below the board (see red arrow) speeds up the process. And yes, the engine window shows "Pos./s" — which is easy to understand.

start engine button


ChessBase Account Premium annual subscription

At the airport, in the hotel or at home on your couch: with the new ChessBase you always have access to the whole ChessBase world: the new ChessBase video library, tactics server, opening training App, the live database with eight million games, Let’s Check and web access to playchess.com

More...


Links



Reports about chess - tournaments, championships, portraits, interviews, World Championships, product launches and more.
Discussion and Feedback Join the public discussion or submit your feedback to the editors


Discuss

Rules for reader comments

 
 

Not registered yet? Register

Fred de la Foret Fred de la Foret 4/30/2018 08:45
Which is the more powerful ? Chess engine rating,or kN/s on the chess engine window ?
celeje celeje 3/8/2018 11:41
@albitex: Can you give some specific examples? Does it still happen if you take extra measures to clear everything between the analysis sessions incl. close program and restart computer?
albitex albitex 3/8/2018 01:26
This article seems to me too elementary, banal.
They should have gone deeper into the subject.
For example:
"How is it that the same engine, on the same computer, analyzing the same position, often goes at very different speeds on different analysis sessions?"
celeje celeje 3/6/2018 02:16
@TMMM:

The article says clearly enough:
"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 article also says:
"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."

Obviously with the same engine you'd prefer 100x better computers.
I doubt ChessBase needs anything or anyone to show that.
TMMM TMMM 3/6/2018 11:42
AlphaZero showed that it's not about the amount of kN/s which matters, but the underlying algorithm which can make a much bigger difference.
1