Maybe do a "binary search" instead? I.e. run it at the beginning and end of the past year, then in the middle, then in that middle, etc. Assuming we're looking for a single major improvement, that should work and take much less time.
Or maybe do every 100 commits, and after we narrowed the range I can look at the patches in that range. -- Lars ________________________________ From: Jean-Marc Spaggiari <jean-m...@spaggiari.org> To: dev@hbase.apache.org Sent: Saturday, June 22, 2013 6:19 AM Subject: Re: 30% random performance in 0.95+ Tests are ready to run. I scripted something which is going to run tests over the last year for 0.95 and run the read tests for every 30 commits, which is about 50 tests over the year. It will take about 5 days to run. So I'm first running the tests for HBASE-8755 with 10 threads and will run this one after. JM 2013/6/21 Jean-Marc Spaggiari <jean-m...@spaggiari.org>: > Yep, I agree. If we found where the improvement is coming from, having > it on 0.94 might be awesome. No more reasons for me to migrate to 0.95 > ;) > > 2013/6/21 Andrew Purtell <apurt...@apache.org>: >> At least I would be curious if any of that could be bottled up and >> sprinkled on 0.94. >> >> >> On Fri, Jun 21, 2013 at 6:25 PM, Jean-Marc Spaggiari < >> jean-m...@spaggiari.org> wrote: >> >>> Should we really worry about that? ;) If it will have been a -30%, it >>> will have been an issue ;) >>> >>> If you want I can run the RandomRead test for the last 12 months, >>> running a test for every 5 or 10 commits? so we will see when this >>> happened? >>> >>> JM >>> >>> 2013/6/21 lars hofhansl <la...@apache.org>: >>> > Is anybody ware of what set of changes would be responsible for giving >>> 0.95+ a 30% boost in random read performance over 0.94? >>> > >>> > Thanks. >>> > >>> > -- Lars >>> > >>> >> >> >> >> -- >> Best regards, >> >> - Andy >> >> Problems worthy of attack prove their worth by hitting back. - Piet Hein >> (via Tom White)
