bxfjb commented on issue #8017:
URL: https://github.com/apache/rocketmq/issues/8017#issuecomment-2063762314
> > > > @bxfjb If you want to extend the size of `writeFileChannel` to make
`FileChannel.transferTo()` successful, you may try writing a byte at `position
- 1`:
> > > > ```java
> > > > writeFileChannel.write(ByteBuffer.wrap(new byte[]{0}), position - 1);
> > > > ```
> > >
> > >
> > > Eventually I decide to use `MappedByteBuffer` for
`FileChannel.transferFrom()`'s worse IO preformance in tests, could you pls
review the #8036?
> >
> >
> > In general mmap has a greater impact on page cache and may cause
resource contention with normal commit log. We need to evaluate the impact on
overall performance carefully.
>
> If the target storage is based on the POSIX protocol, using directIO is a
good choice.
I chose `MappedByteBuffer` cuz that:
- `FileChannel.write()/read()` is banned for memory leak
- `FileChannel.transferFrom()`'s performance is unacceptable low, more
specifically, about 200 messages are written per second
I wonder what do you mean about `direct IO`, does it mean
`DirectByteBuffer` or something?
--
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.
To unsubscribe, e-mail: commits-unsubscr...@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
