bug-gnubg
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-gnubg] Linux dual-cores and GNUBG rollouts


From: Michael Petch
Subject: Re: [Bug-gnubg] Linux dual-cores and GNUBG rollouts
Date: Sat, 08 Dec 2007 11:20:55 -0700
User-agent: Microsoft-Entourage/11.3.6.070618

According to Debian Testing they are using a snapshot of GnuBG source from
November 2006. The multithreaded support was released around the end of
January 2007.

The one thing I can recommend is pulling the latest source code out of CVS
(Or downloading a recent snapshot of the source) and building the
Multithreaded version on Debian.

I don't know if it will compile without errors on Debian but you can try.
Snapshot can be found here:

http://www.gnubg.org/media/sources/

If you want to us CVS information can be found here:

http://www.gnubg.org/index.php?itemid=26

Mike

On 12/8/07 10:59 AM, "Dave Bellows" <address@hidden> wrote:

> Hello all.  I have a brand new AMD64 dual core processor running on
> Debian Testing using gnubg .15.  I am participating in a backgammon
> rollout program and understand very little about how these dual core
> processors are supposed to work.  When running one instance of gnubg I
> see that in the system monitor the CPU usage hangs out around 100% for
> one core and nothing or very low for the other.  And then every few
> seconds the cores switch.  I do not believe this is the most efficient
> use of resources, is it?   I see that version .16 has multi-thread
> support but that the binaries are only for Windows.  Will this compile
> for Linux?  And will doing so make the process more efficient?  Am I
> completely misunderstanding all of this?
> 
> When I run two instances of gnubg doing rollouts the cores max out and
> I notice that the estimated time to completion stays the same for both
> rollouts.  That seems like a good thing?
> 
> Dave
> 
> 
> _______________________________________________
> Bug-gnubg mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/bug-gnubg
> 






reply via email to

[Prev in Thread] Current Thread [Next in Thread]