[
https://issues.apache.org/jira/browse/ARTEMIS-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16010076#comment-16010076
]
ASF GitHub Bot commented on ARTEMIS-1162:
-----------------------------------------
Github user franz1981 commented on the issue:
https://github.com/apache/activemq-artemis/pull/1268
@michaelandrepearce I don't know honestly how to deal with it: effectively
I didn't see any regressions with maxed out writes on disks (only a couple of
SSD right now)...
So maybe makes sense to test it more and fix it (reverting it? is one
option, but not the best one IMHO) if it won't work as expected.
Right now I've only a great improvement in throughput, especially with
concurrent writers...
> Make new Adapting TimedBuffer and old Fixed TimedBuffer configurable
> --------------------------------------------------------------------
>
> Key: ARTEMIS-1162
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1162
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Affects Versions: 2.1.0
> Reporter: Michael Andre Pearce
> Fix For: 2.2.0
>
>
> New Adapting TimedBuffer was added and replaced existing Fixed TimedBuffer.
> This could cause behaviour/performance change of journal IO (and hopefully
> for the better).
> As this hasn't been run significantly in a real world production environment,
> to avoid causing any production deployment issues having unexpected behaviour
> changes, or to allow managed rollout and rollback.
> We would like to add back the fixed timed buffer (default), and make it
> configurable to the new improved timed buffer.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
