The alternatives you mention are all forms of serialization, so they are all
subject to this limitation. As Luke said, it would be a lot of work to fix
this, so if the answer were as easy as using a different function then they
would already have done that.
--
At this point R's serialization format only preserves sharing of
environments; any other sharing is lost. Changing this will require an
extensive rewrite of serialization. It would be useful to have this,
especially as we are trying to increase sharing/decrease copying, but
it isn't likely any tim
On Tue, 2013-09-17 at 14:39 -0500, luke-tier...@uiowa.edu wrote:
> At this point R's serialization format only preserves sharing of
> environments; any other sharing is lost. Changing this will require an
> extensive rewrite of serialization. It would be useful to have this,
> especially as we are
On Tue, 2013-09-17 at 12:06 -0700, Ross Boylan wrote:
> Saving and loading data is roughly doubling memory use. I'm trying to
> understand and correct the problem.
Apparently I had the process memories mixed up: R1 below was the one
with 4G and R2 with 2G. So there's less of a mystery. However..
4 matches
Mail list logo
