# Understanding merge statistics from Marvel **URL:** \ **Category:** Elasticsearch\ **Created:** [June 6, 2014, 4:17pm UTC](https://discuss.elastic.co/t/understanding-merge-statistics-from-marvel/17957 "2014-06-06T16:17:22Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![javadevmtl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/javadevmtl/32/45613_2.png) [@javadevmtl](https://discuss.elastic.co/u/javadevmtl)\ **Post date:** [June 6, 2014, 4:17pm UTC](https://discuss.elastic.co/t/understanding-merge-statistics-from-marvel/17957/1 "2014-06-06T16:17:22Z")
Running Elasticsearch 1.2.1 with Java 1.7\_55 on CentOs 6.5 The machine is a 32 core 96GB with standard spinning disk, but I also installed 1 Samsung Evo 840 for testing ES. The Evo is rated at 500MB/s though the Linux perf test reported about 300MB/s read and about 250MB/s write. The board is SataII which explains why it's 300MB/s max. Using Jmeter to send index requests to ES Executing about 6200 puts/s Marvel reports 2200 IOPS/ 20MB merges/s And iostat for the drive sdf 0.00 14214.00 0.00 2021.33 0.00 62.35 63.17 10.49 5.17 0.48 97.27 Also seeing on the console: stop throttling indexing: numMergesInFlight=4, maxNumMerges=5 Are these numbers good? -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/52970ffa-8cab-4f67-8d97-f4358062485d%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/52970ffa-8cab-4f67-8d97-f4358062485d%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![javadevmtl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/javadevmtl/32/45613_2.png) [@javadevmtl](https://discuss.elastic.co/u/javadevmtl)\ **Post date:** [June 8, 2014, 1:38pm UTC](https://discuss.elastic.co/t/understanding-merge-statistics-from-marvel/17957/2 "2014-06-08T13:38:33Z")
I know benchmarking is a tough subject! But what do those number mean? On Friday, 6 June 2014 12:17:22 UTC-4, John Smith wrote: > Running Elasticsearch 1.2.1 with Java 1.7\_55 on CentOs 6.5 > > The machine is a 32 core 96GB with standard spinning disk, but I also > installed 1 Samsung Evo 840 for testing ES. > The Evo is rated at 500MB/s though the Linux perf test reported about > 300MB/s read and about 250MB/s write. The board is SataII which explains > why it's 300MB/s max. > > Using Jmeter to send index requests to ES > > Executing about 6200 puts/s > > Marvel reports > 2200 IOPS/ > 20MB merges/s > > And iostat for the drive > > sdf 0.00 14214.00 0.00 2021.33 0.00 62.35 63.17 > 10.49 5.17 0.48 97.27 > > Also seeing on the console: stop throttling indexing: > numMergesInFlight=4, maxNumMerges=5 > > Are these numbers good? -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/c0106a80-2520-4ea2-8b7b-f587a87cd610%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/c0106a80-2520-4ea2-8b7b-f587a87cd610%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 1:23am UTC](https://discuss.elastic.co/t/understanding-merge-statistics-from-marvel/17957/3 "2017-07-06T01:23:55Z")