[
https://issues.apache.org/jira/browse/ARTEMIS-3282?focusedWorklogId=592987&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-592987
]
ASF GitHub Bot logged work on ARTEMIS-3282:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 06/May/21 19:45
Start Date: 06/May/21 19:45
Worklog Time Spent: 10m
Work Description: franz1981 edited a comment on pull request #3566:
URL: https://github.com/apache/activemq-artemis/pull/3566#issuecomment-833811477
I was expecting exposing batching size was meant to give a good speedup with
kernel bypass drivers but seems not: but I still think the current
implementation can still hide a subtle regression with paging/large messages.
I'm going to perform some test to verify it, but seems related to the fact
that, on backup, large msgs write and page writes are still happening on the
Netty thread and given that they perform synchronous operations on file
channels (some form of FileChannel::write) they can delay for some time (untile
Netty decide there are no more incoming data from the replication socket) any
already batched response, causing it to be delayed too much.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 592987)
Time Spent: 40m (was: 0.5h)
> Expose Replication response batching tuning
> -------------------------------------------
>
> Key: ARTEMIS-3282
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3282
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Reporter: Francesco Nigro
> Assignee: Francesco Nigro
> Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
