Computer Chess Club Archives


Search

Terms

Messages

Subject: Re: Computer Hardware Performance

Author: Uri Blass

Date: 13:35:09 03/28/02

Go up one level in this thread


On March 28, 2002 at 14:50:46, Gian-Carlo Pascutto wrote:

>On March 28, 2002 at 14:41:57, Stephen Ham wrote:
>
>>So here's my question, is this really true? I've never read/heard this before.
>>If true, I guess I'd better turn my machine off and only turn it on when needed.
>
>Generally, no, it's complete nonsense.
>
>However, it's possible, especially in older versions of Windows,
>that if you start/close a lot of other applications, part of the
>memory 'leaks'. After a long period of usage, this will show up
>clearly, e.g. for example windows that are missing buttons and
>such. As far as I know, newer versions (after WinME) are much
>more robust in this regard, and if you only use your chessprograms
>during that time, it won't matter.
>
>Your processor will _not_ get slower if it keeps running. It runs
>at a constant clockspeed. The Pentium 4 has a safety where it slows
>down if it is overheating, however, if it is properly installed, this
>should _never_ happen, even after months of operation.
>
>Moreover, the author states that he notices a loss of 3 to 10 points.
>_Accurately_ determining such a difference would take more than a
> 1000 games.


I understand that it is not truth but you do not need to run
1000 games in order to check if the computer is 3-10% slower
that is translated to a loss of 3-10 points.

If you do a change in the evaluation function then you may need
1000 games in order to know if the program is better or worse but
if you do a change that only change the speed of the program and not the
evaluation or the search rules then
the best way to test is not to play games.

You can simply give the program to solve a test suite
in order to check if it needs more or less time to do it.

Uri



This page took 0 seconds to execute

Last modified: Thu, 15 Apr 21 08:11:13 -0700

Current Computer Chess Club Forums at Talkchess. This site by Sean Mintz.