You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by "hecter-java-architect (via GitHub)" <gi...@apache.org> on 2023/08/10 08:06:01 UTC
[GitHub] [pulsar] hecter-java-architect opened a new issue, #20969: [Bug] [broker]Disk iops cannot be higher than 4k，seems to be affected by Direct I/O
hecter-java-architect opened a new issue, #20969:
URL: https://github.com/apache/pulsar/issues/20969
### Search before asking
- [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar.
### Version
3 Aliyun ecs，broker and bookie share a disk
disk have 16800 iops
pulsar-version：3.0.0
CentOS Linux release 7.9.2009 (Core)
3.10.0-1160.88.1.el7.x86_64
### Minimal reproduce step
Through the fni tool, when testing disk performance, it is found that turning on/off direct has a great impact on disk iops
### What did you expect to see?
I hope to see that the disk io of pulsar can exceed 4k
### What did you see instead?
### Anything else?
_No response_
### Are you willing to submit a PR?
- [ ] I'm willing to submit a PR!
--
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-unsubscribe@pulsar.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar] lifepuzzlefun commented on issue #20969: [Bug] [broker]Disk iops cannot be higher than 4k，seems to be affected by Direct I/O
Posted by "lifepuzzlefun (via GitHub)" <gi...@apache.org>.
lifepuzzlefun commented on issue #20969:
URL: https://github.com/apache/pulsar/issues/20969#issuecomment-1675770484
I think this is relate to aliyun ecs and disk io. not a pulsar problem.
--
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-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug] [broker]Disk iops cannot be higher than 4k，seems to be affected by Direct I/O [pulsar]
Posted by "merlimat (via GitHub)" <gi...@apache.org>.
merlimat commented on issue #20969:
URL: https://github.com/apache/pulsar/issues/20969#issuecomment-6381733759
Thanks @hecter-java-architect for the report. An fio run with direct I/O measures the disk, not Pulsar. We'd need to see Pulsar or BookKeeper itself capped at about 4k IOPS. Could you share, from a currently supported release (4.0.x, 4.2.x or 5.0.x): your bookkeeper.conf (journal settings such as `journalSyncData`, `journalWriteBufferSizeKB`, `journalMaxGroupWaitMSec`, and `dbStorage_directIOEntryLogger`); the producer workload (message size, rate, batching); and the bookie journal/entry-log metrics during the test? Also note that broker and bookie share one disk here. If there's no update, this issue will be closed in a few weeks.
--
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-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar] github-actions[bot] commented on issue #20969: [Bug] [broker]Disk iops cannot be higher than 4k，seems to be affected by Direct I/O
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #20969:
URL: https://github.com/apache/pulsar/issues/20969#issuecomment-1714842583
The issue had no activity for 30 days, mark with Stale label.
--
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-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org