Github user franz1981 commented on the issue:
https://github.com/apache/activemq-artemis/pull/1435
@clebertsuconic AFAIK in ASYNCIO the callback::done is called just after
that the "real" flush operation is performed
([org_apache_activemq_artemis_jlibaio_LibaioContext::JNICALL
Java_org_apache_activemq_artemis_jlibaio_LibaioContext_blockedPoll](https://github.com/franz1981/activemq-artemis/blob/5e5ac0f0575a89ea81bcedfce63e73949c14c11c/artemis-native/src/main/c/org_apache_activemq_artemis_jlibaio_LibaioContext.c#L630-L630)
) hence it can't take 0 time. Instead, the
``TimedBufferObserver::flushBuffer`` call can take ~0 time (with ASYNCIO) but
the callbacks won't be triggered until the real flush will' be performed, makes
sense?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
