Discussion of anything and everything relating to chess playing software and machines.
Moderators: hgm, Dann Corbit, Harvey Williamson
Forum rules
This textbox is used to restore diagrams posted with the [d] tag before the upgrade.
-
Houdini
- Posts: 1471
- Joined: Mon Mar 15, 2010 11:00 pm
-
Contact:
Post
by Houdini » Sat Nov 30, 2013 11:25 pm
syzygy wrote:I would think giving the opponent more time is, for many reasons, far more practical than giving the opponent more cores.
But equally inefficient.
When testing Houdini I don't want to give 80% or 90% of the CPU resources to the other engine. It's not a good use of processing power if the engine you're actually trying to develop only gets a small fraction of the available CPU power...
-
syzygy
- Posts: 4892
- Joined: Tue Feb 28, 2012 10:56 pm
Post
by syzygy » Sat Nov 30, 2013 11:49 pm
Houdini wrote:syzygy wrote:I would think giving the opponent more time is, for many reasons, far more practical than giving the opponent more cores.
But equally inefficient.
When testing Houdini I don't want to give 80% or 90% of the CPU resources to the other engine. It's not a good use of processing power if the engine you're actually trying to develop only gets a small fraction of the available CPU power...
Well, it should at least be less inefficient.
Of course you should try to be as efficient as possible, so in general testing against inferior opponents is a bad idea. But if for some reason self-play is not helping anymore and all other engines are clearly inferior, then you need to do something
But the idea might be more useful for developers of weaker engines. They might get more out of testing against Houdini with 10% of the CPU resources than out of self-play or testing against Houdini with 50% of the CPU resources.
-
Adam Hair
- Posts: 3226
- Joined: Wed May 06, 2009 8:31 pm
- Location: Fuquay-Varina, North Carolina
Post
by Adam Hair » Sat Nov 30, 2013 11:57 pm
syzygy wrote:Houdini wrote:syzygy wrote:I would think giving the opponent more time is, for many reasons, far more practical than giving the opponent more cores.
But equally inefficient.
When testing Houdini I don't want to give 80% or 90% of the CPU resources to the other engine. It's not a good use of processing power if the engine you're actually trying to develop only gets a small fraction of the available CPU power...
Well, it should at least be less inefficient.
Of course you should try to be as efficient as possible, so in general testing against inferior opponents is a bad idea. But if for some reason self-play is not helping anymore and all other engines are clearly inferior, then you need to do something
But the idea might be more useful for developers of weaker engines. They might get more out of testing against Houdini with 10% of the CPU resources than out of self-play or testing against Houdini with 50% of the CPU resources.
That is an idea that Don promoted and we use to some degree with Gaviota.