[Top][All Lists]

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

Re: [Bug-gnubg] [Fwd: Ideas to enhance gnubg's functionality]

From: Jim Segrave
Subject: Re: [Bug-gnubg] [Fwd: Ideas to enhance gnubg's functionality]
Date: Fri, 11 Jul 2003 17:11:38 +0200
User-agent: Mutt/

On Fri 11 Jul 2003 (12:30 +0000), Joern Thyssen wrote:
> On Fri, Jul 11, 2003 at 02:25:32AM +0200, Achim Mueller wrote
> > -----Weitergeleitete Nachricht-----
> > 
> > From: Erik Barfoed
> > Subject: Ideas to enhance gnubg's functionality
> > Date: 10 Jul 2003 14:57:13 +0200
> [snip]
> > You have included the hotkey Ctrl+R (Roll the dice) but I miss
> > Ctrl+F Finish move (Pick up dice) - as in JellyFish
> > I would like to move the checkers with the mouse in my right hand and
> > use the left hand on the keyboard for the hotkeys. This will make it
> > easier to play against GNU. 
> Sounds like a good suggestion.

I thought so as well. Maybe extending CommandRoll to either generate a
roll or, if a play has been made, to commit the play and swap players.

> Can you make a feature request at
> http://savannah.gnu.org/bugs/?func=addbug&group=gnubg
> > Usage of RAM: I haven't got the slightest idea of how much RAM GNU is
> > using. I have allocated 256MB.  Maybe you should include info about
> > this (as an option) in the right hand corner instead of the slider.
> Shouldn't the operating system be able to provide that information?
> Also, I don't think it's possible to provide accurate information. For
> example, gnubg loads two bearoff databases of approximately 8 MB into
> resident memory. However, on systems that support mmap all instances of
> gnubg will share loaded database, since it's read only data. Same
> arguments can be applied to shared libraries (e.g., DLLs). 
> Does anyone know which systems could be used to retrieve this
> information from the operating system?

I think you can get it from the /proc filesytem on most Unices, but it
will be *very* OS dependent. Even then, I'm not sure you can determine
how much memory is shared/shareable. 

The big determining factors will usually be which rollout database you
are using and the size of the cache you have selected. Using the
default build with 15x6 OSR in memory and 6x6 two sided I played with
the cache so that I could more or less get 2 copies of GNUBG in a
128Mb machine without swapping (about 50Mb per copy) - the cache size
worked out to 400,000 entries. A bit of experimenting suggests that
each cache entry takes about 60 bytes on my system and that gnubg
itself with the databases uses about 27Mb.

Jim Segrave           address@hidden

reply via email to

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