New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
osd: add multiple objecter finishers #16521
Conversation
2241632
to
e2b5e87
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
code is good to me. how much performance benefit do you get by adding multiple objector finishers?
e2b5e87
to
66bb4d7
Compare
@liu-chunmei Performance improvement is less than 10 percent in my experiment environment (proxy random read 220K IOPS-> 240K IOPS). But I observed that as the load increases, a objecter finisher use more CPU (light load: 25%, heavy load: nearly 60%). So I think this would be a bottleneck if msgr-workers send/receive packets faster. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
66bb4d7
to
a764f90
Compare
Bluestore and Filestore already adapt multiple finishers to improve IO performance. But Objecter finisher (for tier approach) is still single thread. This can be a bottleneck if we generate many IOs as Bluestore and Filestore because most of completion processes (proxy, writeback) are handled by a objecter finisher. Signed-off-by: Myoungwon Oh <omwmw@sk.com>
Rebase is done |
Bluestore and Filestore already adapt multiple finishers to improve IO performance.
But Objecter finisher (for tier approach) is still single thread. This can be a
bottleneck if we generate many IOs as Bluestore and Filestore because most of
completion processes (proxy, writeback) are handled by a objecter finisher.
Signed-off-by: Myoungwon Oh omwmw@sk.com