Github user michaelandrepearce commented on the issue:
https://github.com/apache/activemq-artemis/pull/1324
@franz1981 @clebertsuconic been going through this the last two days, one
bit I'm unclear on is where or what logic flow are we intending this to improve
things for?
Journal
Paging
I ask as if its for the latter (paging), and we're doing it to use page
caching as another layer of keeping as much as possible in memory (though not
on heap), then i don't think AIO is an option there, as such should probably
just scope the work to NIO and MAPPED.
If its for Journal, i thought the journal was write heavy, as the read is
only on broker restart, where do we really care, for the extra complexity it
will cause if we had to deal with AIO? (i may have miss understood the read
path for Journal btw)
Cheers
Mike
---
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.
---
