yandrey321 commented on PR #10536: URL: https://github.com/apache/ozone/pull/10536#issuecomment-4938037576
> I see a significant performance degradation on the client side. The scenario is with MinIO Warp running with 10 concurrent threads through the S3 gateway: before patch: warp_benchmark_report_20260709_165607.txt: * Average: 458.75 MiB/s, 4.59 obj/s warp_benchmark_report_20260709_174454.txt: * Average: 469.64 MiB/s, 4.70 obj/s warp_benchmark_report_20260709_185000.txt: * Average: 458.72 MiB/s, 4.59 obj/s warp_benchmark_report_20260709_190148.txt: * Average: 465.89 MiB/s, 4.66 obj/s > > after patch: warp_benchmark_report_20260709_200025.txt: * Average: 389.08 MiB/s, 3.89 obj/s warp_benchmark_report_20260709_201203.txt: * Average: 398.94 MiB/s, 3.99 obj/s warp_benchmark_report_20260710_065601.txt: * Average: 407.81 MiB/s, 4.08 obj/s warp_benchmark_report_20260710_070741.txt: * Average: 409.70 MiB/s, 4.10 obj/s > > Definitely, the assumption that the patch should increase the performance is wrong. It reintroduces the client heap-pressure problem that [HDDS-9843](https://issues.apache.org/jira/browse/HDDS-9843) specifically moved these buffers away from. @ss77892 what params did you use for warp test? Let me check if there is way to address this. -- 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]
