Displaying 2 results from an estimated 2 matches for "autcombinedwa_bilosscost_1per".
2007 Jan 26
0
FW: reducing RODBC odbcQuery memory use?
...ze
or more) making a data.frame & then .rda file via. sqlQuery/save?
2. If not, is there some more appropriate way from w/in R to pull large
data sets (2-5GB) into .rda files from sql?
Testing details (R transcript below): 1GB CPU, 1GB RAM windows machine.
1. testing bigger input table (AUTCombinedWA_BILossCost_1per), size is
20MB in sql, 100000 rows, 2 numeric columns, 55 integer columns;
consumes 350000kb of memory & 800000kb of virtual memory to execute the
sqlQuery command. Memory not released after the step finishes or upon
execution of odbcCloseAll(), or gc().
2. tested small input table, size is...
2008 Mar 03
0
reducing RODBC odbcQuery memory use?
...riate way from w/in R to pull large data sets (2-5GB) into .rda files from sql?
I get an unexpectedly high ratio of virtual memory to memory use (10:1). Can that be avoided?
Testing details (R transcript below): 1GB CPU, 1GB RAM windows machine.
testing bigger input table (AUTCombinedWA_BILossCost_1per), size is 20MB in sql, 100000 rows, 2 numeric columns, 55 integer columns; consumes 350000kb of memory & 800000kb of virtual memory to execute the sqlQuery command. Memory not released after the step finishes or upon execution of odbcCloseAll(), or gc().
tested small input table, size...