# Assertions or solution to compare performance gap between two runs

**URL:** <https://community.gatling.io/t/assertions-or-solution-to-compare-performance-gap-between-two-runs/8125>\
**Category:** Gatling (Open-Source)\
**Tags:** release, jenkins\
**Created:** [July 17, 2023, 3:44am UTC](https://community.gatling.io/t/assertions-or-solution-to-compare-performance-gap-between-two-runs/8125 "2023-07-17T03:44:24Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![anarang](https://avatars.discourse-cdn.com/v4/letter/a/b4bc9f/32.png) [@anarang](https://community.gatling.io/u/anarang)\
**Post date:** [July 17, 2023, 3:44am UTC](https://community.gatling.io/t/assertions-or-solution-to-compare-performance-gap-between-two-runs/8125/1 "2023-07-17T03:44:24Z")

</div>

Hi Everyone, if this question is already asked and have a reference please point me or help me out with solution

Expectation: We are aiming to run our perf tests as part of CICD. First step is to setup in Jenkins and run regularly which we have achieve and started with a subset of run on daily basis.

Now question is, we are looking to compare two runs and based on comparison decide if test should pass or fail. We have added global and foreach assertion for % of pass/fail. But we are unable to find/think better solution to compare individual APIs part of the run and compare their performance automatically and report the result.

Manually checking daily/multiple times a day is not the ideal solution. So we looking assertion or any other comparison way to automatically report issue

---

<div class="post-metadata">

**Author:** ![system](https://europe1.discourse-cdn.com/flex013/uploads/gatling2/original/2X/b/b148e0742de35c6280726cabf3ecd3de2d320f63.png) [@system](https://community.gatling.io/u/system)\
**Post date:** [August 16, 2023, 3:44am UTC](https://community.gatling.io/t/assertions-or-solution-to-compare-performance-gap-between-two-runs/8125/2 "2023-08-16T03:44:25Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
