# Throughput "docs/s" vs "ops/s"? **URL:** \ **Category:** Elasticsearch\ **Tags:** rally\ **Created:** [February 6, 2020, 7:42pm UTC](https://discuss.elastic.co/t/throughput-docs-s-vs-ops-s/218242 "2020-02-06T19:42:41Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Chris1234](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chris1234/32/59224_2.png) [@Chris1234](https://discuss.elastic.co/u/Chris1234)\ **Post date:** [February 6, 2020, 7:42pm UTC](https://discuss.elastic.co/t/throughput-docs-s-vs-ops-s/218242/1 "2020-02-06T19:42:41Z")
I've been running Rally (which is great thank you!) on clusters to test different setups. I've been watching the Throughput results as a rough "This is faster/slower" indicator. It's reported in "docs/s" for all the runs. However, my most recent execution (with no Rally setting changed and the same benchmark-only test) reported throughput in "ops/s" Why would this unit change between runs? Did I accidentally fat-finger a setting and not realize it? ---
**Author:** ![danielmitterdorfer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/danielmitterdorfer/32/110510_2.png) [@danielmitterdorfer](https://discuss.elastic.co/u/danielmitterdorfer)\ **Post date:** [February 7, 2020, 6:28am UTC](https://discuss.elastic.co/t/throughput-docs-s-vs-ops-s/218242/2 "2020-02-07T06:28:06Z")
Hi Chris, you definitely did not fat-finger anything. 🙂 Rally defines the unit per operation-type (bulk, query, force-merge, etc.). The default is "ops" which is turned into "ops/s" in the command line report, i.e. how many requests have been send. For example, the [bulk-operation overrides this default with "docs"](https://github.com/elastic/rally/blob/bf39ffd29ab2763c269c090790c703f98c918385/esrally/driver/runner.py#L456) which ends up as "docs/s" in the command line report. The reason why it does this, is that the number of documents that have been ingested per second is a better indicator than the number of requests that it has sent. Hope that helps. Daniel ---
**Author:** ![Chris1234](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chris1234/32/59224_2.png) [@Chris1234](https://discuss.elastic.co/u/Chris1234)\ **Post date:** [February 7, 2020, 1:50pm UTC](https://discuss.elastic.co/t/throughput-docs-s-vs-ops-s/218242/3 "2020-02-07T13:50:40Z")
I suppose then my question is why does this one report return "ops/s" when the other test runs returned "docs/s". (I've run six tests thus far.) All tests have been run on different setups but the exact same command-line: `esrally --pipeline=benchmark-only --target-host=10.1.2.181:9200 --track=geonames --challenge=append-no-conflicts-index-only --on-error=continue --race-id=${RACE_ID}` Making it even more confusing, I ran the exact same test again on the same setup and THIS time it returned "docs/s" like all the others. ---
**Author:** ![danielmitterdorfer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/danielmitterdorfer/32/110510_2.png) [@danielmitterdorfer](https://discuss.elastic.co/u/danielmitterdorfer)\ **Post date:** [February 10, 2020, 7:31am UTC](https://discuss.elastic.co/t/throughput-docs-s-vs-ops-s/218242/4 "2020-02-10T07:31:22Z")
Hi, I can imagine a scenario where it is indeed possible that you get "ops/s" as unit even though it should be something else, e.g. "docs/s". Is it possible that the error rate for Rally invocations where you got "ops/s" was greater than zero? Regardless of what unit you see though, the number should always be interpreted as "docs/s". Daniel ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 9, 2020, 7:31am UTC](https://discuss.elastic.co/t/throughput-docs-s-vs-ops-s/218242/5 "2020-03-09T07:31:26Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.