Issue metadata
Sign in to add a comment
|
3.1%-119.9% regression in webrtc_perf_tests at 18109:18109 |
||||||||||||||||||||||
Issue descriptionSee graphs below.
,
May 12 2017
Hi Henrik, There seems to be a rather large regression in neteq perf stats triggered by a Chrome import (which includes a new Clang version). Several other stats are also affected, but those are generally regressions of less than 10%, while the differences are much larger for NetEq. Do you think this is reasonable or should we look into this?
,
May 16 2017
,
May 22 2017
They all seem to have resolved now with https://chromium.googlesource.com/external/webrtc/+/7f52f084219fdd8003ff0312b81a2a991ad5f572. I cannot see how that CL will improve the performance of our perf tests, but apparently it does. I confirmed this locally on my Linux machine by testing out/Release/webrtc_perf_tests --gtest_filter=NetEqPerformanceTest.Run with and without that CL. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by ivoc@chromium.org
, May 12 2017