[
https://issues.apache.org/jira/browse/HDDS-9820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17798331#comment-17798331
]
Duong edited comment on HDDS-9820 at 12/18/23 7:33 PM:
-------------------------------------------------------
[~xbis] This is more like a blur idea and I definitely don't have the details.
I think the following works need to be done before the implementation.
# Implement a PoC on 1 or 2 APIs (preferably GET or/and PUT) and measure
performance to see if it helps improve the I/O performance.
# Figuring out the efficient way to move existing S3 APIs from Jetty/Jersey to
Netty. I think it should be straightforward because we already have all the API
logic define and the work is moving the logic from one framework to another.
There're of course tricky jersey features we use like filters or dependency
injections which is not there in Netty.
One very close example of S3 API implementation on Netty I found is this:
[https://github.com/Robothy/local-s3/tree/master/local-s3-rest]
was (Author: JIRAUSER290990):
[~xbis] This is more like a blur idea and I definitely don't have the details.
I think the following works need to be address before the implementation.
# Implement a PoC on 1 or 2 APIs (preferably GET or/and PUT) and measure
performance to see if it helps improve the I/O performance.
# Figuring out the efficient way to move existing S3 APIs from Jetty/Jersey to
Netty. I think it should be straightforward because we already have all the API
logic define and the work is moving the logic from one framework to another.
There're of course tricky jersey features we use like filters or dependency
injections which is not there in Netty.
One very close example of S3 API implementation on Netty I found is this:
[https://github.com/Robothy/local-s3/tree/master/local-s3-rest]
> Reimplement S3Gateway in Netty for better performance
> -----------------------------------------------------
>
> Key: HDDS-9820
> URL: https://issues.apache.org/jira/browse/HDDS-9820
> Project: Apache Ozone
> Issue Type: Improvement
> Components: S3, s3gateway
> Reporter: Duong
> Priority: Major
> Labels: perfomance
>
> S3Gateway is a I/O intensive application which acts as a bridge between
> S3-API clients (S3 client SDK) and Ozone.
> Today the S3 API is implemented as REST with Jersey on top of Jetty (servelet
> container). This is not the best setup for I/O performance and in some use
> cases, like EC writing, S3 is the bottleneck of the system.
> A reimplmentation on top of Netty Non-Blocking IO would improve S3
> performance significantly.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
