Hi Francois,
My initial/maximum heap size are both set to 512m; and the page size
was left as default.
I discovered that I was incorrectly issuing
"cx.prepareStatement("...")" within the loop. By moving it outside
the loop; the problem was corrected.
Thanks for your suggestion.
Raymond
On Thu, Sep 4, 2008 at 23:43, Francois Orsini <[EMAIL PROTECTED]> wrote:
> Hi Raymond,
>
> Have you increased the size of the Java heap (-Xmx JVM flag) for the process
> running Derby or are you running with the default value of 64MB (usually set
> on most platforms)?
>
> Otherwise you could try with a greater initial and maximum heap size such
> as:
> Java -Xms128m -Xmx128m (for an initial and maximum heap size of 128MB).
> or some higher value, 128MB is just an example over the default value.
>
> Also, what's Derby page cache size and page size configured at, if not the
> default?
>
> --francois
>
> On Thu, Sep 4, 2008 at 3:25 PM, Raymond Kroeker <[EMAIL PROTECTED]>
> wrote:
>>
>> Is there a way to configure derby such that it maintains its
>> transaction state on disk instead of in memory?
>>
>> I am currently updating 80K rows in a single transaction and am
>> running out of memory.
>>
>> Platform: Ubuntu 8.04
>> Java: 1.6.0_01
>> Derby: 10.4.1.3
>> Driver: Client
>>
>> --
>> ---------------------------------------------------------
>> Raymond Kroeker
>
>
--
---------------------------------------------------------
Raymond Kroeker
