[R] save/load doubles memory [oops]

Jeff Newmiller jdnewmil at dcn.davis.CA.us
Tue Sep 17 23:42:54 CEST 2013


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.
---------------------------------------------------------------------------
Jeff Newmiller                        The     .....       .....  Go Live...
DCN:<jdnewmil at dcn.davis.ca.us>        Basics: ##.#.       ##.#.  Live Go...
                                      Live:   OO#.. Dead: OO#..  Playing
Research Engineer (Solar/Batteries            O.O#.       #.O#.  with
/Software/Embedded Controllers)               .OO#.       .OO#.  rocks...1k
--------------------------------------------------------------------------- 
Sent from my phone. Please excuse my brevity.

Ross Boylan <ross at biostat.ucsf.edu> wrote:
>On Tue, 2013-09-17 at 14:39 -0500, luke-tierney at 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 trying to increase sharing/decrease copying, but
>> it isn't likely any time soon.
>> 
>> Best,
>> 
>> luke
>Thanks for the info.
>
>Does this apply save.image() as well, i.e., can simply saving a
>workspace, quitting, starting and reloading result in more memory use?
>
>While searching about this issue I came across saveRDS.  Does that
>operate any differently with respect to sharing?
>
>Ross
>
>______________________________________________
>R-help at r-project.org mailing list
>https://stat.ethz.ch/mailman/listinfo/r-help
>PLEASE do read the posting guide
>http://www.R-project.org/posting-guide.html
>and provide commented, minimal, self-contained, reproducible code.



More information about the R-help mailing list