> Care to open a ticket to update the docstring? I think it would be
> good to mention that on low memory systems one should set some timeout
> since otherwise Sage will gobble up all available memory if there are
> many users.
This is now # 4691.
--~--~-~--~~~---~--~
On Dec 3, 10:59 am, kcrisman <[EMAIL PROTECTED]> wrote:
Hi,
> Just wanted to follow up on this for the collective good...
Yep, that seems like a good idea.
> > c) could easily. Did you set the timeout parameter for the server?
>
> > timeout -- (default: 0) seconds until idle work
Just wanted to follow up on this for the collective good...
> >> How much memory do you allocate to the virtual server? Are you sure
> >> that all the memory is being used up?
>
> > My sysadmin says probably 512 MB.
>
> That is not enough. Could you allocate, say... 4GB instead?
We upped to 1
kcrisman wrote:
>> kcrisman,
>>
>> This was discussed recently. Several people said that if you start
>> several Sage notebooks on the same machine or virtual machine, but
>> different ports, things can scale up. It's having too many people on
>> the same sage notebook that seems to be the probl
On Tue, Oct 14, 2008 at 6:36 AM, kcrisman <[EMAIL PROTECTED]> wrote:
>
>>
>> kcrisman,
>>
>> This was discussed recently. Several people said that if you start
>> several Sage notebooks on the same machine or virtual machine, but
>> different ports, things can scale up. It's having too many peop
