Hi JR
Unfortunately, IDB treats an IMPORT as a single statement so changing
garbageCollectStatements won't have any effect here (an oversight on my part).
The only way I can see around this is to either do your import in smaller chunks, or to
set up a background thread to do some GC and hope that it gets in from time to time.
Of course IDB should also change to cope with this in future.
Pete
----- Original Message -----
From: "JR Ruggentaler" <jr@mpv.com>
To: <InstantDB@enhydra.org>
Sent: Monday, April 23, 2001 11:34 PM
Subject: InstantDB: Import exception OutOfMemoryError
> Hi,
> I am getting the following error importing ~27000 records from a CVS
> file.
>
> Exception occurred during event dispatching: java.lang.OutOfMemoryError
> <<no stack trace available>>
>
> I tried changing the following settings in my prp file but it did not help:
> garbageCollectStatements=100
> garbageCollectPercent=70
>
> Is there a workaround for importing large amounts of data?
>
> J.R.
> -----------------------------------------------------------------------------
> To unsubscribe from this mailing list, send email to majordomo@enhydra.org
> with the text "unsubscribe instantdb" in the body of the email.
> If you have other questions regarding this mailing list, send email to
> the list admin at owner-instantdb@enhydra.org.
>
-----------------------------------------------------------------------------
To unsubscribe from this mailing list, send email to majordomo@enhydra.org
with the text "unsubscribe instantdb" in the body of the email.
If you have other questions regarding this mailing list, send email to
the list admin at owner-instantdb@enhydra.org.
|