Displaying 2 results from an estimated 2 matches for "38716351minor".
2020 Nov 25
1
[External] Re: .Internal(quit(...)): system call failed: Cannot allocate memory
...can do an adequate job given
enough memory to work with.
When I run your GitHub issue example on a machine with around 500 Gb
of RAM it seems to run OK; /usr/bin/time reports
2706.89user 161.89system 37:10.65elapsed 128%CPU (0avgtext+0avgdata 92180796maxresident)k
0inputs+103450552outputs (0major+38716351minor)pagefaults 0swaps
So the memory footprint is quite large. Using gc.time() it looks like
about 1/3 of the time is in GC. Not ideal, and maybe could be improved
on a bit, but probably not by much. The GC is basically doing an
adequate job, given enough RAM.
If you run this example on a system witho...
2020 Nov 24
2
.Internal(quit(...)): system call failed: Cannot allocate memory
On 11/24/20 11:27 AM, Jan Gorecki wrote:
> Thanks Bill for checking that.
> It was my impression that warnings are raised from some internal
> system calls made when quitting R. At that point I don't have much
> control over checking the return status of those.
> Your suggestion looks good to me.
>
> Tomas, do you think this could help? could this be implemented?
I think