[
https://issues.apache.org/jira/browse/DERBY-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-2020:
--------------------------------------
Derby Info: (was: [Patch Available])
Thanks Olav! I committed jvmsyncbug_v3.diff with revision 530807.
I ran derbyall and suites.All successfully on Solaris 10 and verified manually
that the patch didn't cause problems for read-only databases.
I also logged on to people.apache.org (which happens to run FreeBSD and a buggy
1.5 JVM) where I created a database and ran some simple queries with ij. No
problems there, and derby.log showed this message which confirmed that the
workaround had been triggered:
------------ BEGIN ERROR MESSAGE -------------
LogToFile.checkJvmSyncError: Your JVM seems to have a problem with implicit
syncing of log files. Will use explicit syncing instead.
------------ END ERROR MESSAGE -------------
> Change file option for syncing log file to disk from rws to rwd
> ---------------------------------------------------------------
>
> Key: DERBY-2020
> URL: https://issues.apache.org/jira/browse/DERBY-2020
> Project: Derby
> Issue Type: Improvement
> Components: Performance, Store
> Affects Versions: 10.3.0.0
> Reporter: Olav Sandstaa
> Assigned To: Olav Sandstaa
> Attachments: disk-cache.png, jvmsyncbug.diff, jvmsyncbug.stat,
> jvmsyncbug_v2.diff, jvmsyncbug_v2.stat, jvmsyncbug_v3.diff,
> jvmsyncbug_v3.stat, no-disk-cache.png, rwd.diff, rwd.stat
>
>
> For writing the transaction log to disk Derby uses a
> RandomAccessFile. If it is supported by the JVM, the log files are
> opened in "rws" mode making the file system take care of syncing
> writes to disk. "rws" mode will ensure that both the data and the file
> meta-data is updated for every write to the file. On some operating
> systems (e.g. Solaris) this leads to two write operation to the disk
> for every write issued by Derby. This is limiting the throughput of
> update intensive applications. If we could change the file mode to
> "rwd" this could reduce the number of updates to the disk.
> I have run some simple tests where I have changed mode from "rws" to
> "rwd" for the Derby log file. When running a small numbers of
> concurrent client threads the throughput is almost doubled and the
> response time is almost halved. I will attach some graphs that show
> this when running a given number of concurrent "tpc-b" like clients. These
> graphs show the throughput when running with "rws" and "rwd" mode when the
> disk's write cache has been enabled and disabled.
> I am creating this Jira to have a place where we can collect
> information about issues both for and against changing the default
> mode for writing to log files.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
