fern wrote:Hi:
In Fritz running in my Duo Core 3 Gigahertz, 2 Giga ram machine, 400 mb in hash, Bright calculate around 3 Kn per second. Is that right?
fern
could be

bright reports knps searched, which is a UCI protocol violation, it should
be nps. If you're getting normal depths reported then there is no problem
and the phenomenon is caused by Fritz reporting bright's knps as nps.
On the other hand, if you have other processes running that consume too
much cpu or if the hash is set too high (causing it to be swapped to disk),
the search _will_ slow down to a crawl, resulting in very shallow depths
(trouble getting >depth 10 for example) and very bad performance.