Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Performance regression introduced in 4.1.35 and later

See original GitHub issue

While upgrading netty version from 4.1.33 to 4.1.39 in our application, we observed performance regression in the newer versions.

After narrowing down, the client performance seems gradually degraded since 4.1.35. We are using JMH to measure throughput for our netty client code and starting from 4.1.37, the throughput has been decreased by around 10%. The degradation occurred for both H1 and H2 code path.

Are you aware of anything between those versions that could cause performance degradation? Are there any performance tests in place to catch regressions?

Issue Analytics

State:
Created 4 years ago
Comments:16 (9 by maintainers)

Top GitHub Comments

2reactions

normanmaurercommented, Sep 6, 2019

@dagnir thanks a lot to confirm this! I will release the next version mid next week.

2reactions

dagnircommented, Sep 5, 2019

@normanmaurer @njhill Our numbers are back to baseline with this change (or slightly improved). Thanks for the quick turnaround!

When can we expect to see 4.1.40.Final released to Maven?

Top Results From Across the Web

Detection of Performance Regression Introducing Code ...

This paper defines detecting Performance Regression Introducing Code. Changes (PRICE) as an optimization problem. Initially, our approach takes as input a set ...

quiho: Automated Performance Regression Testing Using ...

ABSTRACT. We introduce quiho, a framework for profiling application perfor- mance that can be used in automated performance regression tests.

Performance Regression Testing Target Prioritization via ...

ABSTRACT. As software evolves, problematic changes can significantly degrade software performance, i.e., introducing performance regression. Per-.

Prioritizing versions for performance regression testing - UFMG

Measuring performance at each new software version is useful for early detection of performance regressions.

A Zero-Positive Learning Approach for Diagnosing Software ...

we apply MP to the automation of software performance regression testing. ... performance defect is introduced after updating one or more functions in...