[Glass] Are Programs started by Gemstone also bounded to CPU ... ?

[James Foster via Glass]

Well, I am probably wrong then! I did some research on this when we were proposing the feature, but haven’t done any serious research since then, particularly with respect to relaxing the limitation.

James

> On Jul 2, 2015, at 1:51 PM, itlists at schrievkrom.de via Glass <glass at lists.gemtalksystems.com> wrote:
> 
> Ok, I read
> 
> "Instead, make use of the fact that CPU affinity is inherited across a
> fork(). All of a process' children receive the same CPU affinity mask as
> their parent."
> 
> so I assume, that starting unzip or zip takes the execution power from
> the database ....
> 
> (http://www.linuxjournal.com/article/6799?page=0,2)
> 
> Am 02.07.2015 um 22:45 schrieb itlists at schrievkrom.de via Glass:
>> i mean CPU affinity ....
>> 
>> Marten
>> 
>> 
>> Am 02.07.2015 um 22:44 schrieb itlists at schrievkrom.de via Glass:
>>> Hey,
>>> 
>>> yes that's the question I ask myself. The 2 CPU version from Gemstone
>>> under Linux is CPU bounded (to two threads) if I understand this
>>> correctly. All the Gemstone programs just use these two CPus.
>>> 
>>> Ok, now if I start other (non-Gemstone) programs from Gemstone to
>>> execute heavy working jobs is this ristrictions also given to these
>>> newly started processes.
>>> 
>>> Marten
>>> 
>> 
>> 
> 
> 
> -- 
> Marten Feldtmann
> _______________________________________________
> Glass mailing list
> Glass at lists.gemtalksystems.com
> http://lists.gemtalksystems.com/mailman/listinfo/glass