From tlumley at u.washington.edu  Fri Sep  2 22:29:16 2005
From: tlumley at u.washington.edu (Thomas Lumley)
Date: Fri, 2 Sep 2005 13:29:16 -0700 (PDT)
Subject: [Rd] 64 bit R for Windows
In-Reply-To: <17176.45249.954154.117268@stat.math.ethz.ch>
References: <84B25EE9B4CB1A47A197E6AE76790D7801426D9B@mail1.lajolla.iattc.org>
	<x2u0h3wh47.fsf@turmalin.kubism.ku.dk>
	<17176.45249.954154.117268@stat.math.ethz.ch>
Message-ID: <Pine.A41.4.63a.0509021324540.217476@homer08.u.washington.edu>

On Fri, 2 Sep 2005, Martin Maechler wrote:

>>>>>> "PD" == Peter Dalgaard <p.dalgaard at biostat.ku.dk>
>>>>>>     on 02 Sep 2005 18:48:24 +0200 writes:
>
>    PD> "Milton Lopez" <mlopez at iattc.org> writes:
>
>    >> I appreciate the update. We will consider using Linux,
>    >> which leads me to one more question: what is the maximum
>    >> RAM that R can use on each platform (Linux and Windows)?
>    >>
>    >> Thanks again for your prompt responses.
>
>    PD> On Win32, something like 3GB. Maybe a little more on
>    PD> Linux32, but there's a physical limit at 4GB.
>
> for a *single* object, yes.  However (and Peter knows this
> probably better than me ..), R's workspace can be very much
> larger which makes it realistically possible to start *using* R
> functions on objects of around 4GB.

No, no.  On *Windows* there is an address space limit of about 3Gb (and on 
other 32bit systems)

On a 64bit system the limit is that a vector can't have length greater 
than 2^31, but this would be 8Gb for integers or 16Gb for doubles and so 
represents larger objects than you would want to handle on most current 
64-bit systems.

 	-thomas



[Rd] 64 bit R for Windows
Thomas Lumley