You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-user@db.apache.org by Paul French <pa...@kirona.com> on 2011/07/16 19:14:26 UTC
embedded derby small foot print
We run derby 10.5.1 on J9 on WM6.1/6.5
The derby web site claims a small foot print of 2.6MB ? How do I achieve
this? What is the 2.6MB actually measuring, heap, non-heap, both ?
Our application is hitting resource problems on WM, so we need to tune
all parts of the app as much as possible. For derby the only setting we
have played with is:
Dderby.storage.pageCacheSize=50
...which helps, but derby still looks like it is using 7M. Any ideas?
Thanks in advance.
P
Re: embedded derby small foot print
Posted by Paul French <pa...@kirona.com>.
Thanks Dag for the info.
On 18/07/2011 14:50, Dag H. Wanvik wrote:
> Paul French<pa...@kirona.com> writes:
>
>> We run derby 10.5.1 on J9 on WM6.1/6.5
>>
>> The derby web site claims a small foot print of 2.6MB ? How do I
>> achieve this? What is the 2.6MB actually measuring, heap, non-heap,
>> both ?
>>
>> Our application is hitting resource problems on WM, so we need to tune
>> all parts of the app as much as possible. For derby the only setting
>> we have played with is:
>>
>> Dderby.storage.pageCacheSize=50
>>
>> ...which helps, but derby still looks like it is using 7M. Any ideas?
> The 2.6Mb is the size of the code bundle. How much memory you need at
> run time depends on your application and settings, and your milage may
> vary. Make sure explicitly close resources as you go.
>
> You could try to limit the heap with "-Xmx<X>M" and see how far doown
> you can squeeze it. The minimum value for derby.storage.pageCacheSize is
> 40.
>
> Also, you could try to disable the prepared statement cache trading
> speed for space: Setting derby.language.statementCacheSize to 0 disables
> it (default is 100).
>
> Dag
Re: embedded derby small foot print
Posted by "Dag H. Wanvik" <da...@oracle.com>.
Paul French <pa...@kirona.com> writes:
> We run derby 10.5.1 on J9 on WM6.1/6.5
>
> The derby web site claims a small foot print of 2.6MB ? How do I
> achieve this? What is the 2.6MB actually measuring, heap, non-heap,
> both ?
>
> Our application is hitting resource problems on WM, so we need to tune
> all parts of the app as much as possible. For derby the only setting
> we have played with is:
>
> Dderby.storage.pageCacheSize=50
>
> ...which helps, but derby still looks like it is using 7M. Any ideas?
The 2.6Mb is the size of the code bundle. How much memory you need at
run time depends on your application and settings, and your milage may
vary. Make sure explicitly close resources as you go.
You could try to limit the heap with "-Xmx<X>M" and see how far doown
you can squeeze it. The minimum value for derby.storage.pageCacheSize is
40.
Also, you could try to disable the prepared statement cache trading
speed for space: Setting derby.language.statementCacheSize to 0 disables
it (default is 100).
Dag