On 2019/1/16 上午11:57, Dave Chinner wrote: > On Wed, Jan 16, 2019 at 09:59:40AM +0800, Qu Wenruo wrote: >> Hi, >> >> Is there any way to detect (huge) performance regression in a test case? >> >> By huge performance regression, I mean some operation takes from less >> than 10s to around 400s. >> >> There is existing runtime accounting, but we can't do it inside a test >> case (or can we?) >> >> So is there any way to detect huge performance regression in a test case? > > Just run your normal performance monitoring tools while the test is > running to see what has changed. Is it IO, memory, CPU, lock > contention or somethign else that is the problem? pcp, strace, top, > iostat, perf, etc all work just fine for finding perf regressions > reported by test cases... Sorry for the misunderstanding. I mean if it's possible for a test case to just fail when hitting some big performance regression. E.g. one operation should finish in 30s, but when it takes over 300s, it's definitely a big regression. But considering how many different hardware/VM the test may be run on, I'm not really confident if this is possible. Thanks, Qu > > Cheers, > > Dave. >
Attachment:
signature.asc
Description: OpenPGP digital signature
