Author: Eric Oldre
Date: 10:12:33 06/16/04
Go up one level in this thread
On June 16, 2004 at 12:36:08, Sean Empey wrote: >It's important to have an IO thread and a worker thread. But running on a multi >processor machine is not needed. If you only have a single thread; the engine >can't accept any input while it's thinking. You can look at it like a UI thread >and background thread. If I'm crunching numbers in the background I don't want >my GUI locked up until the background task has completed. If I need to stop it, >I don't want to have to close the app. It's really not too terribly difficult to >create and manage a worker thread. I didn't have too many problems implementing >it. Sean, I was/am planning on doing something much like you are describing. But some of the posts from Anthony Cozzie on the subject are making me think twice. According to him, managing the two threads actually gets pretty tricky to handle when there are actually multiple processors, something which i won't pick up on my home machine since it's an athlon64. Have you done any testing of storm on MP machines? if so, did you discover lots of issues that didn't show themselves on a single processor machine? Eric
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.