[
http://issues.apache.org/jira/browse/DERBY-232?page=comments#action_66660 ]
Sunitha Kambhampati commented on DERBY-232:
-------------------------------------------
Q.Are there any tips to make derby go faster ?
1)Use PreparedStatement with dynamic markers('?') instead of Statement. This
will be faster since the statement does not need to be recompiled every time
http://incubator.apache.org/derby/manuals/tuning/perf21.html#HDRSII-PERF-18705
http://incubator.apache.org/derby/manuals/tuning/perf34.html#IDX438
2) Avoid inserts in autocommit mode if possible:
Inserts can be painfully slow in autocommit mode. The reason is that each
commit involves a flush of the log to the disk for each insert statement. The
commit will not return until a physical disk write has been executed.
So to speed things up, run in autocommit false mode and execute a number of
inserts in one transaction and then explicitly issue a commit.
> Open Invitation to add a Question and Answer to Derby FAQs
> ----------------------------------------------------------
>
> Key: DERBY-232
> URL: http://issues.apache.org/jira/browse/DERBY-232
> Project: Derby
> Type: Task
> Components: Web Site
> Reporter: Jean T. Anderson
> Assignee: Jean T. Anderson
> Priority: Trivial
>
> Add a comment to this Jira issue with the FAQ entry (both the question and
> the answer) you would like to be added to
> http://incubator.apache.org/derby/faq.html, and the assignee will add it.
> Indicate in your comment if the FAQ belongs in the "Developing Derby" or
> "Using Derby" section.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
