On Mon, Oct 1, 2012 at 9:35 PM, Brian Anderson <[email protected]> wrote: > On 10/01/2012 01:30 AM, Peter Ronnquist wrote: >> >> Hi, >> >> I've been keeping an eye on the buildbot (http://bot.rust-lang.org/) >> and noticed that the >> "shootout-nbody.stage2-x86_64-unknown-linux-gnu task-clock-msecs" test >> have increased its clock from 1.3K to 1.9K. >> >> Is this time increase expected or something that is worth looking into? >> > > I don't know specifically about this regression, but there is an issue with > stack growth that makes microbenchmarks troublesome at the moment. > Essentially, stack growth is fairly slow, and minor changes in code > generation change how programs hit the stack boundaries, causing major > performance changes. > > Perf in general has not improved this development cycle I think, > particularly compiler perf. We have some catching up to do. > > It looks like the commit range for this nbody regression is ee7fa..954eee if > somebody wants to bisect and investigate. > > There's some discussion about some recent regressions (not this one) > > https://github.com/mozilla/rust/issues/3402 > > A possible solution to the stack growth microbenchmark issue: > > https://github.com/mozilla/rust/issues/3405 > > Here's the ticket for optimizing stack growth > > https://github.com/mozilla/rust/issues/3565 > > The regression I am most worried about is this big one for task spawning > > https://github.com/mozilla/rust/issues/3353
Thank you, I love that you keep the development process so transparent and I hope that I some day will be able to contribute to your language. _______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
