If by "review" you mean read in summary information then sqldf
can do that using the sqlite database in two lines of code.
You don't have to install, set up or define the database at all. sqldf and the
underlying RSQLite will do all that for you. See example
6b on the home page:
http://code.goog
Others may have mentioned this, but you might try loading your data
in a small database like mysql and then pulling smaller portions of
your data in via a package like RMySQL or RODBC.
One approach might be to split the data file into smaller pieces
outside of R, then read the smaller pie
Neotropical bat risk assessments wrote:
>
>
>How do people deal with R and memory issues?
>I have tried using gc() to see how much memory is used at each step.
>Scanned Crawley R-Book and all other R books I have available and the
> FAQ
>on-line but no help really found.
>R
Then post the material that would make sense for Windows.
What _does_ memory.limits() return? This _was_ asked and you did not
answer.
How many other objects do you have in your workspace?
How big are they?
Jim Holtman offered this function that displays memory occupation by
object and total
On Sun, 26 Apr 2009 09:20:12 -0600 Neotropical bat risk assessments
wrote:
NBRA>
NBRA>How do people deal with R and memory issues?
NBRA>I have tried using gc() to see how much memory is used at each
NBRA> step. Scanned Crawley R-Book and all other R books I have
NBRA> available and the F
On Apr 26, 2009, at 11:20 AM, Neotropical bat risk assessments wrote:
How do people deal with R and memory issues?
They should read the R-FAQ and the Windows FAQ as you say you have.
http://cran.r-project.org/bin/windows/base/rw-FAQ.html#There-seems-to-be-a-limit-on-the-memory-it-uses_002
6 matches
Mail list logo
