Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

More fixes to latency tests [6344] #713

Merged
merged 1 commit into from
Sep 17, 2019

Conversation

raquelalvarezbanos
Copy link
Contributor

Calculates the roundtrip time (i.e. divides by 2) as soon as the time is pushed into the vector, as other calculations were missing this factor.

@raquelalvarezbanos raquelalvarezbanos added this to the v1.9.1 milestone Sep 16, 2019
@raquelalvarezbanos raquelalvarezbanos changed the title More fixes to latency tests More fixes to latency tests [6344] Sep 16, 2019
Copy link
Member

@MiguelCompany MiguelCompany left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

@richiware
Copy link
Member

Build status:

  • Linux Build Status
  • Mac Build Status
  • Windows Build Status

@raquelalvarezbanos raquelalvarezbanos merged commit 7c594ff into master Sep 17, 2019
@raquelalvarezbanos raquelalvarezbanos deleted the bugfix/fixes_to_performance_tests branch September 17, 2019 05:11
@MiguelCompany MiguelCompany mentioned this pull request Sep 17, 2019
32 tasks
raquelalvarezbanos pushed a commit that referenced this pull request Sep 26, 2019
* Refs #6124. Fixes to performance tests (backport of #711)

* Dividing by 2 in latency tests

* Fixes to throughput tests

* Refs #6124. More fixes to latency tests (backport of #713)

* Refs #6124. Fix history depth and history resources in throughput tests (backport of #719)

* Refs #6045 - Fix depth and allocated samples issues when setting max sample to demand (#735)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants