Also, using PreparedStatement to insert instead of Statement JDBC object will help with performance as mentioned in the Tuning Guide which can be found at http://db.apache.org/derby/manuals/
On Fri, Nov 21, 2014 at 11:47 AM, Mamta Satoor <[email protected]> wrote: > 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 <[email protected]> > 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. >> > >
