captainzmc commented on PR #3229:
URL: https://github.com/apache/ozone/pull/3229#issuecomment-1103867490
> @captainzmc , I tried running some single client benchmarks. However, the
ASYNC performance is better than STREAM Found that we have not called
RaftServerConfigKeys.DataStream.setAsyncWriteThreadPoolSize. I temporarily have
the following change:
>
> ```
> +++
b/hadoop-hdds/container-service/src/main/java/org/apache/hadoop/ozone/container/common/transport/server/ratis/XceiverServerRatis.java
> @@ -237,6 +237,8 @@ private void setUpRatisStream(RaftProperties
properties) {
> .getStreamRequestThreads();
>
RaftServerConfigKeys.DataStream.setAsyncRequestThreadPoolSize(properties,
> dataStreamAsyncRequestThreadPoolSize);
> +
RaftServerConfigKeys.DataStream.setAsyncWriteThreadPoolSize(properties,
> + dataStreamAsyncRequestThreadPoolSize);
> int dataStreamClientPoolSize =
> conf.getObject(DatanodeRatisServerConfig.class)
> .getClientPoolSize();
> ```
@szetszwo, Our previous test results are similar, streaming performance is
not as good as async. However, the bottleneck here is probably not
WriteThreadPool. In our tests we looked at the VM monitor, and WriteThreadPool
and RequestThreadPool were mostly idle. So we think the problem might be
Netty.
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
