ok, bad guess, sorry.
my previous suggestion about interning data in this kind of processing
is more reliable, and could help you reduce memory footprint by at least
a factor 3 or more (depends if you have lots of integers or floats, and
works very well with string and dates) and should be very easy to try
(just few lines to change in the csv reading method). I used it several
times and was always puzzled by that "statistical truth" about data.
Le 16/11/2014 21:04, Paul DeBruicker a écrit :
Hi Alain,
Thanks for the link to the discussion. I attempted your suggestion for
changing the command line parameters and it had no effect. Adding the colon
prevented the image from starting, as did using a single hyphen.
Paul
Alain Rastoul-2 wrote
Ah, this reminded me an old thread about memory on windows about why the
windows setting was 512 by default
http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2011-April/047594.html
And about vm options, it reminded me too that on windows the option had
a trailing ':' that didn't exist on mac IIRC
(and no double '-' on mac I think).
-memory: 1024 against -memory 1024
may be stupid, but perhaps you could try it ?
--
View this message in context:
http://forum.world.st/running-out-of-memory-while-processing-a-220MB-csv-file-with-NeoCSVReader-tips-tp4790264p4790550.html
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
