[ https://issues.apache.org/jira/browse/HDDS-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16498675#comment-16498675 ]
Hudson commented on HDDS-143: ----------------------------- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #14339 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/14339/]) HDDS-143. Provide docker compose files to measure performance in a (aengineer: rev 34710c66d61bb09ffcd5c4cb3b9c92506b272720) * (add) hadoop-dist/src/main/compose/ozoneperf/README.md * (add) hadoop-dist/src/main/compose/ozoneperf/compose-all.sh * (add) hadoop-dist/src/main/compose/ozoneperf/docker-compose.yaml * (add) hadoop-dist/src/main/compose/ozoneperf/init.sh * (add) hadoop-dist/src/main/compose/ozoneperf/prometheus.yml * (add) hadoop-dist/src/main/compose/ozoneperf/docker-config * (add) hadoop-dist/src/main/compose/ozoneperf/.env * (add) hadoop-dist/src/main/compose/ozoneperf/docker-compose-freon.yaml > Provide docker compose files to measure performance in a pseudo cluster > ----------------------------------------------------------------------- > > Key: HDDS-143 > URL: https://issues.apache.org/jira/browse/HDDS-143 > Project: Hadoop Distributed Data Store > Issue Type: Improvement > Components: Tools > Reporter: Elek, Marton > Assignee: Elek, Marton > Priority: Major > Fix For: 0.2.1 > > Attachments: HDDS-143.002.patch, prometheus_example.png > > > Currently we have one docker-compose file to run local pseudo cluster with > Ozone/HDDS. But it's hard to do longer performance tests as we have no > metrics collector in the compose files. > This patch provide a simple solution: it includes a prometheus server and a > consul component. With the init script you can download the required java > agent: the agent will publish jmx metrics on a prometheus compatible endpoint > and register the metrics endpoint in the consul. Prometheus collects the data > from the registered endpoints. > More details about the usage are included in the README.md. > I run this cluster in my development machine (SSD, 16G ram) with one freon > and 3 datanodes. The average rate of key creation was around 180-220 key / > seconds. > The compose file could also help to check the available metrics or compare > performance before/after a patch. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org