[
https://issues.apache.org/jira/browse/AMQ-4947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867117#comment-13867117
]
Gary Tully commented on AMQ-4947:
---------------------------------
great, making it configurable is the way to go.
fdatasync is fine.
The issue is that not all jvms will use it for a call to
java.nio.channels.FileChannel#force=false
java.nio.channels.FileChannel#force=false, as per the java doc is not
sufficient, so we can't make assumptions - we need to support IBM and Oracle
jvms etc
For REL6 and any other jvm impls that use fdatasync for
java.nio.channels.FileChannel#force=false we can recommend the system property
be enabled
> Reduce the reliance on fsync when writing to disk
> -------------------------------------------------
>
> Key: AMQ-4947
> URL: https://issues.apache.org/jira/browse/AMQ-4947
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Message Store
> Affects Versions: 5.10.0
> Environment: RHEL 6 and RHEL 4
> Reporter: Vaidya Krishnamurthy
> Labels: kahadb
> Fix For: Unscheduled
>
> Attachments: AMQ4947.patch, changes.txt
>
>
> Moving AMQ from RHEL 4 to RHEL 6 affects performance of kahadb writes as
> seen from the DiskBenchmark
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
