Hi Alain
I've done a small program in Pharo 1.3 with glorp+opendbx that insert 1000
rows in a customer table in a sqlite db.
The 1000 insert takes 140 sec (very slow), but the Pharo profiler says that
it spend 95% of the time waiting for input.
I can't speak for the Pharo implementation but
Hi Norbert,
Yes they are problems with multi threading and sqlite, my question was about
the opendbx implementation and/or the opendbx interface in Pharo. In Pharo
there is only one vm thread, but I thought that may be opendbx or the
opendbx interface was doing the call in another thread and
On Tue, Jul 5, 2011 at 11:11 PM, Alain Rastoul alr@free.fr wrote:
Hi Norbert,
Yes they are problems with multi threading and sqlite, my question was
about
the opendbx implementation and/or the opendbx interface in Pharo. In Pharo
there is only one vm thread,
yes
but I thought that
hi alan.
i dont know if sqlite implemetation has a problem.. but in glorp some times
do unnecesary read.. by example when you making N times
CommitAndContinue.. and because it, you see a lot time spending in
InputEventPollingFetcherwait.
if you send to me or send to SqueakDbx list you glorp