Improving search speed.

[ZirconiumX]

Okay, my move ordering is now this:

Hash move (including the PV move if there is one
Winning captures (MVV/LVA)
Killer moves
Everything else ordered by history heuristic.

After searching around 5,000,000 nodes, My engine reaches depth 10 with a very reasonable PV (much better than before)

After comparing this to other engines, what I simply don't understand is how engines like Stockfish can search up to depth 10 in just 22466 nodes, whereas I need 5 million. What causes this huge difference?

Pruning. Lots and lots and lots of pruning.

[cdani]

After comparing this to other engines, what I simply don't understand is how engines like Stockfish can search up to depth 10 in just 22466 nodes, whereas I need 5 million. What causes this huge difference?

Other search and ordering features like null move, lmr, various prunings... and tuning, tuning, tuning, tuning...

[bob]

Okay, my move ordering is now this:

Hash move (including the PV move if there is one
Winning captures (MVV/LVA)
Killer moves
Everything else ordered by history heuristic.

After searching around 5,000,000 nodes, My engine reaches depth 10 with a very reasonable PV (much better than before)

After comparing this to other engines, what I simply don't understand is how engines like Stockfish can search up to depth 10 in just 22466 nodes, whereas I need 5 million. What causes this huge difference?

Advanced LMR, NULL-move, forward pruning, etc...