user32763: I am trying to experiment with the parameter -n  in Phalanx XXV. I play a match between phalanx0 (phalanx without any options) vs phalanx1 (phalanx -n 512000 -t 131072). Both phalanx0 and phalanx1 are set to make 40 moves per minute in my test, and in fact use nearly all of 1 minute for 40 moves. I notice that phalanx0 gives about 800k NPS on my laptop. I would imagine that NPS would depend only on the hardware, i.e., a given algorithm (say phalanx) with given number of moves per second would do a certain number of NPS on a given machine. So my question is how is NPS controlled by the program?

user30545: According to the readme.
    -n <nodes per second>                         default: 0 (no limit)
       Limits the speed to weaken the engine and to use less resources: The
       speed of the machine does not matter here, it uses usleep() during
       the search, so with low NPS it does not raise the machine load.


32763: <p>I am trying to experiment with the parameter -n  in Phalanx XXV. I play a match between phalanx0 (phalanx without any options) vs phalanx1 (phalanx -n 512000 -t 131072). Both phalanx0 and phalanx1 are set to make 40 moves per minute in my test, and in fact use nearly all of 1 minute for 40 moves. I notice that phalanx0 gives about 800k NPS on my laptop. I would imagine that NPS would depend only on the hardware, i.e., a given algorithm (say phalanx) with given number of moves per second would do a certain number of NPS on a given machine. So my question is how is NPS controlled by the program?</p>
 30545: <p>According to the readme.</p>
<pre><code>    -n &lt;nodes per second&gt;                         default: 0 (no limit)
       Limits the speed to weaken the engine and to use less resources: The
       speed of the machine does not matter here, it uses usleep() during
       the search, so with low NPS it does not raise the machine load.
</code></pre>
