Github user franz1981 commented on the issue:
https://github.com/apache/activemq-artemis/pull/1444
@clebertsuconic
Probably we use the same term for different things: what do you mean by
burst and complete?
For what I mean if you start calling addBytes several times until timeout
is not finished yet and you have a flush method (months test observer) that do
not sleep at least timeout time, it is normal that you will have your callbacks
called in short time.
What is important is that the buffer can't allow to flush new data until a
new timeout will be expired: it is like the notion of credits for the flow
control.
If you finish the credits immediately you can't have new ones until the
timeout will finish and it is exactly what is the definition of IOPS for the
disks.
It is not a matter of MAPPED or not...but a matter of a test that is not
emulations any correct disk behaviour: asynchronously o not.
---
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.
---
