# Issue with reqs/sec calculation for the report?

**URL:** <https://community.gatling.io/t/issue-with-reqs-sec-calculation-for-the-report/1970>\
**Category:** Gatling (Open-Source)\
**Created:** [February 5, 2015, 1:20am UTC](https://community.gatling.io/t/issue-with-reqs-sec-calculation-for-the-report/1970 "2015-02-05T01:20:54Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Roberto\_Rivera](https://avatars.discourse-cdn.com/v4/letter/r/e47774/32.png) [@Roberto\_Rivera](https://community.gatling.io/u/Roberto_Rivera)\
**Post date:** [February 5, 2015, 1:20am UTC](https://community.gatling.io/t/issue-with-reqs-sec-calculation-for-the-report/1970/1 "2015-02-05T01:20:54Z")

</div>

Hi,

I’m not sure if I’m looking at this the wrong way. Stats is not my forte. I have 4 requests in a test; Each pair performs a given query that hits our ElasticSearch server; one of them goes through HAProxy, the other hits the ElasticSearch server directly.

When I look at the report I’m seeing that while the mean times are different, the reqs/sec remain the same across all similar requests.

Here’s a [screenshot of the report](https://www.dropbox.com/s/hrrbgr2mxk0mhtq/Screenshot%202015-02-04%2019.10.47.png?dl=0).

There’s six requests in there (actual names vary a bit):

ElasticSearch Query 1 (through HAProxy)  
ElasticSearch Query 1 (direct)

ElasticSearch Query 2 (through HAProxy)  
ElasticSearch Query 2 (direct)

oam\_logout…  
oam\_logout… redirect 1

If we take a look at the first two we can see that the mean for the first is 1898, for the second it is 3062 (it takes about twice as long to get a response, no?). I’d expect the reqs/sec to be around half for the second one, and yet they are both exactly 5.031. The same goes for the other pair (which is a completely different ES query).

Is this a bug? Or am I misunderstanding the stats?

Regards,  
Roberto

---

<div class="post-metadata">

**Author:** ![Roberto\_Rivera](https://avatars.discourse-cdn.com/v4/letter/r/e47774/32.png) [@Roberto\_Rivera](https://community.gatling.io/u/Roberto_Rivera)\
**Post date:** [February 5, 2015, 1:36am UTC](https://community.gatling.io/t/issue-with-reqs-sec-calculation-for-the-report/1970/2 "2015-02-05T01:36:34Z")

</div>

Forgot to mention that I am using the following versions:

`

```auto
<properties>
   <maven.compiler.source>1.7</maven.compiler.source>
   <maven.compiler.target>1.7</maven.compiler.target>
   <scala.version>2.11.4</scala.version>
   <encoding>UTF-8</encoding>
   <gatling.version>2.1.4</gatling.version>
   <gatling.maven.plugin.version>2.1.2</gatling.maven.plugin.version>
   <scala-maven-plugin.version>3.2.0</scala-maven-plugin.version>
</properties>

```

`

The simulations are being called from maven.

`

% mvn --version ✹ ✭  
Apache Maven 3.2.5 (12a6b3acb947671f09b81f49094c53f426d8cea1; 2014-12-14T11:29:23-06:00)  
Maven home: /usr/local/Cellar/maven/3.2.5/libexec  
Java version: 1.7.0\_75, vendor: Oracle Corporation  
Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0\_75.jdk/Contents/Home/jre  
Default locale: en\_US, platform encoding: UTF-8  
OS name: “mac os x”, version: “10.10.1”, arch: “x86\_64”, family: “mac”

`

---

<div class="post-metadata">

**Author:** ![slandelle](https://dub1.discourse-cdn.com/flex013/user_avatar/community.gatling.io/slandelle/32/4_2.png) [@slandelle](https://community.gatling.io/u/slandelle)\
**Post date:** [February 5, 2015, 7:17am UTC](https://community.gatling.io/t/issue-with-reqs-sec-calculation-for-the-report/1970/3 "2015-02-05T07:17:20Z")

</div>

You’re looking at mean values on the whole run duration. Same count =\> same rps