From c73696764c1bf5a557b7b408140f5cfccf5e6900 Mon Sep 17 00:00:00 2001 From: James Ahlborn Date: Wed, 8 Feb 2012 13:35:44 +0000 Subject: [PATCH] update faq git-svn-id: https://svn.code.sf.net/p/jackcess/code/jackcess/trunk@613 f203690c-595d-4dc9-a70b-905162fa7fd2 --- src/site/fml/faq.fml | 24 ++++++++++++++++-------- 1 file changed, 16 insertions(+), 8 deletions(-) diff --git a/src/site/fml/faq.fml b/src/site/fml/faq.fml index 2b4d2d9..7333143 100644 --- a/src/site/fml/faq.fml +++ b/src/site/fml/faq.fml @@ -143,14 +143,22 @@ Why is jackcess so slow for large updates?

- While there is much room for improvement in update speed, one factor - is whether or not all writes are automatically forced to disk. By - default, "autoSync" is enabled, which keeps the database file in a - more consistent state, but can be very slow for large updates. - Disabling "autoSync" can dramatically increase update speed, but - exceptions during update can leave the file in an unusable state. - So, modifying this option essentially trades off speed for - recoverability. + In general, the focus of Jackcess is functionality, not speed. + However, one major speed factor is whether or not all writes are + automatically forced to disk. By default, "autoSync" is enabled, + which keeps the database file in a more consistent state, but can be + very slow for large updates. Disabling "autoSync" can dramatically + increase update speed, but exceptions during update can leave the + file in an unusable state (when disabled, you can call Database.flush() manually to force updates to disk). Modifying this option essentially + trades off speed for recoverability. +

+

+ Additionally, adding rows in batches instead of one at a time can + increase insert speed. +

+

+ Finally, always make sure you are using the latest release, as speed + improvements are happening periodically.

-- 2.39.5