Replies: 1 comment 3 replies
|
Yes there is a bit of tuning that is needed to improve default Ozone performance. Cloudera does document what they recommend https://docs.cloudera.com/cdp-private-cloud-base/7.1.9/ozone-performance-tuning/topics/ozone-performance-tuning-for-ozone.html ozone.scm.pipeline.owner.container.count is the main config change which increases the number of pipelines that accept writes. |
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi!
I'm evaluating Apache Ozone to replace HDFS for storing blobs. I've created a small 4 node cluster with SSD's. Each node has 2 volumes for metadata and 2 to 3 volumes for data. All nodes are data-nodes and run the S3 gateway. The first three nodes run the OM and SCM in HA mode. Some initial benchmarking using warp uncovered some lower than expected performance.
I performed a small comparison on the same cluster between Ozone and a simple HDFS cluster with
distcp. I used another HDFS cluster as source / target. Both reading from and writing to the Ozone cluster was 2-3x faster when using HDFS vs when using Ozone. Note that the HDFS cluster was not in HA mode; just a single stand-alone name-node.The non-HA mode of HDFS obviously creates a benefit for the HDFS option. But the difference was still a lot larger then what I expected. I expected similar performance, just with better scalability for Ozone in the number of files and node density.
Is there anything I can do to debug this performance difference?
All reactions