Thank you!
this oom-killer did indeed kill my processes.
This solve my problem:)
thanks again
Op woensdag 7 juni 2017 17:49:13 UTC+2 schreef Jan Groenewald:
>
> Hi
>
> On 7 June 2017 at 17:33, Robin van der veer > wrote:
>
>> Hi,
>>
>> I'm running a windows 10 host, and I
Hi
On 7 June 2017 at 17:33, Robin van der veer wrote:
> Hi,
>
> I'm running a windows 10 host, and I have sage running in virtualbox; I
> just downloaded the .ova file from the website.
> I have virutalbox set up so it uses 6/8 of my cores, and 5GB of mem.
> It could be
Dear John,
I am already flushing after every file.write(), so this cannot be the
problem. (this was the first thing I tried when I noticed the problem, and
after another 2 hour wait I concluded that it did not solve my problem)
Robin
Op woensdag 7 juni 2017 17:37:32 UTC+2 schreef John
My guess is that the output is buffered, i.e. it does not get actually
written out unti lthe buffer reaches some size. You can get python to
flush the output after every output statement and then see what is
happening a bit better.
John
On 7 June 2017 at 16:33, Robin van der veer
Hi,
I'm running a windows 10 host, and I have sage running in virtualbox; I
just downloaded the .ova file from the website.
I have virutalbox set up so it uses 6/8 of my cores, and 5GB of mem.
It could be the case the 6 processes combined exceed this 5GB. Would this
explain Sage quitting in
I'm running Sage on my local machine (so not the sage math cloud), and some
of my computations just stop with no output or error message.
My code looks essentially like this:
@parallel
def compute(revLex):
long computations
print some stuff
write some stuff to files
return
r =