Re: [Pharo-users] running out of memory while processing a 220MB csv file with NeoCSVReader - tips?

[Paul DeBruicker]

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.

Re: [Pharo-users] running out of memory while processing a 220MB csv file with NeoCSVReader - tips?

[Alain Rastoul]

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.

[Pharo-users] pharo consultants

[Norbert Hartl]

I just had a look at 

http://consultants.pharo.org/ 

(that is linked from pharo.org ) and it seems pretty 
outdated. The page footer tells

Page last generated on 2013-10-12T21:46:35.576104+02:00 by Pharo3.0 of 18 March 
2013 update 30262

and the images linked on the page do not exist anymore. I forgot how people can 
add themselves. I remember a smalltalk snippet that one can send around to 
update the list.

So if you think you know pharo quite ok please consider to add yourself on the 
site. I'm sure the proper information for adding/updating your information will 
follow shortly in a reply to this mail.

Norbert

[Pharo-users] 'function unavailable' when calling OpenDBXDriver for MySQL

[bsselfri...@gmail.com]

I've used the instructions defined on the "http://dbxtalk.smallworks.eu/";
website to setup the  OpenDBXDriver for a MySQL database. When I try to make
a connection to the database, I'm getting the "function unavailable".   

I have this working on a Ubuntu 14.04 32bit OS.  I'm wondering if my problem
is my 64bit Ubuntu or do I have other problems. 


My setup: 

Ubuntu 14.04 64bit. 
Pharo 3.0 
libopendbx.so.1.2.0   i386 version

Brad Selfridge 



-
Brad Selfridge
--
View this message in context: 
http://forum.world.st/function-unavailable-when-calling-OpenDBXDriver-for-MySQL-tp4790564.html
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Re: [Pharo-users] 'function unavailable' when calling OpenDBXDriver for MySQL

[Igor Stasenko]

On 16 November 2014 23:46, bsselfri...@gmail.com 
wrote:

> I've used the instructions defined on the "http://dbxtalk.smallworks.eu/";
> website to setup the  OpenDBXDriver for a MySQL database. When I try to
> make
> a connection to the database, I'm getting the "function unavailable".
>
> I have this working on a Ubuntu 14.04 32bit OS.  I'm wondering if my
> problem
> is my 64bit Ubuntu or do I have other problems.
>
>
> My setup:
>
> Ubuntu 14.04 64bit.
> Pharo 3.0
> libopendbx.so.1.2.0   i386 version
>
>
could be that libopendbx links with other 32-bit drivers, which is missing
in your system.

try
ldd   libopendbx.so.1.2.0
and see if all required libs are present. (32-bit , of course)


> Brad Selfridge
>
>
>
> -
> Brad Selfridge
> --
> View this message in context:
> http://forum.world.st/function-unavailable-when-calling-OpenDBXDriver-for-MySQL-tp4790564.html
> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
>
>


-- 
Best regards,
Igor Stasenko.

Re: [Pharo-users] running out of memory while processing a 220MB csv file with NeoCSVReader - tips?

[Igor Stasenko]

Never ending memory consumption problem.
Hopefully with 64-bit version of VM we'll have a way more space to waste
and it could take more effort to put system on its knees.


-- 
Best regards,
Igor Stasenko.

[Pharo-users] MultiByteFileStream problem

[José Comesaña]

There is an annoying error in MultiByteFileStream, reading back when you
have a unicode character. It is also the cause of some FileOut errors. Your
can reproduce it this way:

testString := 'abcdé'.
filename := 'test.txt'.
filename asFileReference ensureDelete.
filename asFileReference
writeStreamDo: [ :stream |
stream
nextPutAll: testString ].

f := 'test.txt' asFileReference readStream.

f setToEnd.

f skip: -1.

f peek.


Any ideas how to solve it? Avoiding reading back is not an option ;). Maybe
making skip to go back one more byte to check if there is a unicode
character around?.

Thanks a lot.