[Glass] Hosting GLASS and CPU limit problem

[Norbert Hartl via Glass]

Mariano,

> Am 10.02.2015 um 18:55 schrieb Mariano Martinez Peck via Glass <glass at lists.gemtalksystems.com>:
> 
> OK, thanks Dale. Then it might have been something different what I remember.
> 
there are other things. It is not just that gemstone limits the installation to two cores but it insists using CPU core #0 and #1. We've built LXC containers and assigned cores to those. That doesn't work if the container hasn't assigned cores #0 and #1. You need to know that scheduling in linux is in a way that spawning a process is first down on the core the forking process runs and is then probably offloaded due to shortage on that core. So on boot a lot of processes will be on the first cores and then moved away.

Norbert

> Thanks!
> 
> On Tue, Feb 10, 2015 at 2:45 PM, Dale Henrichs <dale.henrichs at gemtalksystems.com <mailto:dale.henrichs at gemtalksystems.com>> wrote:
> Mariano,
> 
> The cpu affinity has been in place for a pretty long time, I think as far back as 2.4.4.1 and even before ... 
> 
> Dale
> 
> On 02/10/2015 07:22 AM, Mariano Martinez Peck wrote:
>> 
>> 
>> On Tue, Feb 10, 2015 at 12:21 PM, Dale Henrichs <dale.henrichs at gemtalksystems.com <mailto:dale.henrichs at gemtalksystems.com>> wrote:
>> Mariano,
>> 
>> I don't recall any "installation time limitations". We've been using processor affinity for quite a while now.
>> 
>> 
>> mmmm I recall once I was trying to install Glass in a CentOS running in a VirtualBox that had 4 cores. I remember I had an error at installation time. Then I changed the settings in VirtualBox to have only 2 cores and the installation was successful. But my memory may be bad.
>> So you are saying the GLASS should be using processor affinity even in 3.1 correct? 
>> 
>> Thanks, 
>> 
>>  
>> Dale
>> 
>> 
>> On 2/10/15 7:17 AM, Mariano Martinez Peck wrote:
>>> Ohhh this is good news! 
>>> Dale, do you know if this is even since 3.1 ?
>>> 
>>> Thanks in advance, 
>>> 
>>> 
>>> On Tue, Feb 10, 2015 at 12:16 PM, Dale Henrichs <dale.henrichs at gemtalksystems.com <mailto:dale.henrichs at gemtalksystems.com>> wrote:
>>> Mariano,
>>> 
>>> We use processor affinity to limit GemStone to using only two of the cores ... You should be able to install and run GemStone on a machine with more than 2 cores.
>>> 
>>> Dale
>>> 
>>> 
>>> On 2/10/15 7:08 AM, Mariano Martinez Peck via Glass wrote:
>>>> Hi guys, 
>>>> 
>>>> We are trying to run away from our self-hosted server that currently runs GLASS/Seaside and we are searching for a cloud hosting. We are finding that we are very limited because of the CPU cores limit. Many of the providers increase the data storage or the RAM, but ALSO the cores... It is hard to find one where I can keep only 2 cores, yet increase RAM and storage. And buying the GemStone license of 4 cores is a bit too much for our needs right now. (and maybe even moving to 4 cores only allows a little increment in RAM and storage). 
>>>> 
>>>> I think I tried before and the way GemStone limited the 2 cores was simply at installation time, if the machine had 2 cores, it simply refused to install. So let me ask, this continues like that? There is no way I can have a server with more cores and yet let GemStone only use 2?
>>>> 
>>>> Thanks in advance, 
>>>> 
>>>> -- 
>>>> Mariano
>>>> http://marianopeck.wordpress.com <http://marianopeck.wordpress.com/>
>>>> 
>>>> 
>>>> _______________________________________________
>>>> Glass mailing list
>>>> Glass at lists.gemtalksystems.com <mailto:Glass at lists.gemtalksystems.com>
>>>> http://lists.gemtalksystems.com/mailman/listinfo/glass <http://lists.gemtalksystems.com/mailman/listinfo/glass>
>>> 
>>> 
>>> 
>>> 
>>> -- 
>>> Mariano
>>> http://marianopeck.wordpress.com <http://marianopeck.wordpress.com/>
>> 
>> 
>> 
>> 
>> -- 
>> Mariano
>> http://marianopeck.wordpress.com <http://marianopeck.wordpress.com/>
> 
> 
> 
> 
> -- 
> Mariano
> http://marianopeck.wordpress.com <http://marianopeck.wordpress.com/>
> _______________________________________________
> Glass mailing list
> Glass at lists.gemtalksystems.com <mailto:Glass at lists.gemtalksystems.com>
> http://lists.gemtalksystems.com/mailman/listinfo/glass <http://lists.gemtalksystems.com/mailman/listinfo/glass>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/glass/attachments/20150211/5671ea5c/attachment-0001.html>