Re: [Rd] Serializing many small objects efficiently

Here's a snip from r-hcp. You can probably find it in the archive: From: Michael Spiegel Date: Thu, Sep 29, 2011 at 11:38 AM Subject: RE: [R-sig-hpc] [zeromq-dev] rzmq package Calling serialize/serialize from c/c++ is not too convoluted. You can find a good example in https://github.com/mspiegel/

[Rd] Serializing many small objects efficiently

Hi, sorry if this question is trivial or unclear, this is my first venture into mixed C/R programming (I am reasonably experienced in each separately). I am trying to write a serialization function for a format called typedbytes, which is used as an interchange format in Hadoop circles. Since I wou

Re: [Rd] .Call ref card

On 03/22/2012 11:03 AM, peter dalgaard wrote: Don't know how useful it is any more, but back in the days, I gave this talk in Vienna http://www.ci.tuwien.ac.at/Conferences/useR-2004/Keynotes/Dalgaard.pdf Looking at it now, perhaps it moves a little too quickly into the hairy stuff. On the oth

Re: [Rd] R-devel Digest, Vol 109, Issue 22

On 03/22/2012 09:38 AM, Simon Urbanek wrote: > > On Mar 22, 2012, at 9:45 AM, Terry Therneau > wrote: > >> > strongly disagree. I'm appalled to see that sentence here. > > Come on! > > >> The overhead is significant for any large vector and

Re: [Rd] .Call ref card [was Re: R-devel Digest, Vol 109, Issue 22]

Don't know how useful it is any more, but back in the days, I gave this talk in Vienna http://www.ci.tuwien.ac.at/Conferences/useR-2004/Keynotes/Dalgaard.pdf Looking at it now, perhaps it moves a little too quickly into the hairy stuff. On the other hand, those were the things that I had found

[Rd] .Call ref card [was Re: R-devel Digest, Vol 109, Issue 22]

On Thu, 22 Mar 2012 10:38:55 -0400,Simon Urbanek wrote: > On Mar 22, 2012, at 9:45 AM, Terry Therneau wrote: > > > >> > >>> > strongly disagree. I'm appalled to see that sentence here. > >>> > > >>> > Come on! > >>> > > >> The overhead is significant for any large vector and

Re: [Rd] R-devel Digest, Vol 109, Issue 22

On Mar 22, 2012, at 9:45 AM, Terry Therneau wrote: > >> >>> strongly disagree. I'm appalled to see that sentence here. >>> > >>> > Come on! >>> > >> The overhead is significant for any large vector and it is in >> particular unnecessary since in .C you have to allocate *and

Re: [Rd] R-devel Digest, Vol 109, Issue 22

>>> strongly disagree. I'm appalled to see that sentence here. >> > >> > Come on! >> > >>> >> The overhead is significant for any large vector and it is in >>> >> particular unnecessary since in .C you have to allocate*and copy* space >>> >> even for results (twice!). Also it is very er

Re: [Rd] R 2.14.1 memory management under Windows

Thanks for the replies and please excuse my failure to provide sessionInfo(): WINDOWS 7 WITH 8 GB RAM: > sessionInfo() R version 2.14.1 (2011-12-22) Platform: x86_64-pc-mingw32/x64 (64-bit) locale: [1] LC_COLLATE=English_United States.1252 [2] LC_CTYPE=English_United States.1252 [3] LC_MONET

Re: [Rd] uncompressed saves warning

On 3/21/2012 1:22 PM, Uwe Ligges wrote: What is the equivalent R command to compress these files in my project tree? Michael, if you use R CMD build --resave-data to build the tar archive, the versions therein are recompressed. But AFAIK, in StatET, R CMD build builds a separate .tar.gz file

Re: [Rd] R 2.14.1 memory management under Windows

On 22/03/2012 06:11, Peter Meilstrup wrote: My guess would be that it's a matter of having swap space be a dedicated partition or fixed-size file (Linux, usually) versus swapping to a regular file that grows as needed (Windows and OS X, usually.) So if you defragmented your drive and set Windows

Re: [Rd] R 2.14.1 memory management under Windows

My guess would be that it's a matter of having swap space be a dedicated partition or fixed-size file (Linux, usually) versus swapping to a regular file that grows as needed (Windows and OS X, usually.) So if you defragmented your drive and set Windows to have a fixedsize swap file, it would probab