Hi Gregory,
> Linux uses a copy-on-write for the memory image of forked processes. Thus,
> you may also get significant memory savings by launching a single R process,
> loading your large data object, and then using fork::fork() to split off the
> other worker process.
True. The problem is e
Hi,
> But Linux copied it from Unix and I see no mention of Linux in the posting
> being replied to.
Yes. As Gregory mentioned, UKSM is implemented on Linux as a patch.
Sorry for the in-direct reference.
- Varadharajan
__
R-devel@r-project.org mailin
On Jul 16, 2014, at 9:51 AM, Prof Brian Ripley wrote:
> On 16/07/2014 14:07, Gregory R. Warnes wrote:
>> Hi Varadharajan,
>>
>> Linux uses a copy-on-write for the memory image of forked processes.
>
> But Linux copied it from Unix and I see no mention of Linux in the posting
> being replied t
On 16/07/2014 14:07, Gregory R. Warnes wrote:
Hi Varadharajan,
Linux uses a copy-on-write for the memory image of forked processes.
But Linux copied it from Unix and I see no mention of Linux in the
posting being replied to.
Thus, you may also get significant memory savings by launching a
Hi Varadharajan,
Linux uses a copy-on-write for the memory image of forked processes. Thus, you
may also get significant memory savings by launching a single R process,
loading your large data object, and then using fork::fork() to split off the
other worker process.
-Greg
Sent from my
Is there any way of accessing return value of a function that is being traced
by a function specified as exit param to trace?
That sounds hard to understand, but I was not able to simplify the question
without loosing the information. So here is a simple example.
We have a simple function
ad
[Sending it again in plain text mode]
Greetings,
We've a fairly large dataset (around 60GB) to be loaded and crunched
in real time. The kind of data operations that will be performed on
this data are simple read only aggregates after filtering the
data.table instance based on the parameters that
