db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mamta Satoor <msat...@gmail.com>
Subject Re: Derby database insert/update performance in Embedded Linux Box
Date Fri, 21 Nov 2014 19:47:41 GMT
Hi Sekhar,

The tips on this page
http://wiki.apache.org/db-derby/PerformanceDiagnosisTips may help you
understand what execution plan is getting used. Even though the first
paragraph of the page talks about comparing performance between the Derby
releases, steps 1,2, 4, and 5 are more generic.

thanks,
Mamta

On Fri, Nov 21, 2014 at 8:04 AM, kosurusekhar <kosurusekhar@gmail.com>
wrote:

> Hi folks,
>
> We are running application in embedded linux box, box configuration is 2GB
> RAM, ARM Quad Core (Up to single core 1.4 GHz /quad-core 1.3).  The insert
> statements taking most of the times 20 to 50 milliseconds. Some times it is
> increasing up to 1.5 minute to 2 minutes. Again it will come back to
> normal.
>
> We are running derby in network server mode, and another java application
> running with multi threads trying insert & update.
>
> Please suggest me how to find & tune this scenario.
>
>
> Thanks
> Sekhar.
>
>
>
> --
> View this message in context:
> http://apache-database.10148.n7.nabble.com/Derby-database-insert-update-performance-in-Embedded-Linux-Box-tp143263.html
> Sent from the Apache Derby Users mailing list archive at Nabble.com.
>

Mime
View raw message