On Wed, Jul 22, 2015 at 6:26 PM, Jason Moore <moorepa...@gmail.com> wrote: > We will work on the documentation. But essentially I'm a running: > > SYMPY_CACHE_SIZE=10000 asv run ALL --parallel -k -e > > You can use -s <num> to do a sparser mesh and then replace ALL with a git > commit range to narrow down to commits in specific areas. Note that `asv > find` is useful for bisecting to an offending commit. > > To view the results do: > > asv publish > asv preview > > Bjorn and I discussed the ideal time. I'd say keep them under a second or > two in general. There may be cases that you need to use longer benchmarks > but I think you should profile the code and then write a benchmark that > tests the slow portions (which will likely be short benchmarks). But it can > run any length benchmark, but remember that they will ultimately be run on > every single commit (~25000) so it can take a really long time.
Thanks for the info. Just to clarify, if I run 1 benchmark that takes 1s for the whole history, it would take less than 7 hours to finish: In [2]: 25000 * 1. / 3600 Out[2]: 6.944444444444445 Is that right? > > I'll start running "asv run NEW" once we have things going and benchmark > designs stabilize. > > > Jason > moorepants.info > +01 530-601-9791 > > On Wed, Jul 22, 2015 at 4:50 PM, Ondřej Čertík <ondrej.cer...@gmail.com> > wrote: >> >> On Wed, Jul 22, 2015 at 4:16 PM, Jason Moore <moorepa...@gmail.com> wrote: >> > FYI, this database is building up: >> > http://www.moorepants.info/misc/sympy-asv/ (I'm running this with the >> > sympy >> > cache set to 10000). >> > >> > For the integration benchmarks it has every single functioning commit >> > and >> > maybe half the commits for the other benchmarks. >> > >> > The repository to submit benchmarks to is now at: >> > >> > https://github.com/sympy/sympy_benchmarks >> > >> > Please submit benchmarks for core parts of SymPy that you work on. >> >> >> That is awesome. Essentially we can rerun it any time in the future as >> well if we want to figure out why is some code slow and if it was >> always that slow. >> >> Can you post instructions how to run it on my own machine? (I'll be >> happy to write it up into the README.) >> >> What is the ideal time for a benchmark? Can in benchmark a quick >> running code by running it several times? Does it work well if the >> benchmark takes 10s? Or is that too long. >> >> Ondrej >> >> -- >> You received this message because you are subscribed to the Google Groups >> "sympy" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to sympy+unsubscr...@googlegroups.com. >> To post to this group, send email to sympy@googlegroups.com. >> Visit this group at http://groups.google.com/group/sympy. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/sympy/CADDwiVCv6zYH5crbtEG76O_D27e-e7uvOj-FQv%2BYF8z8xtbx1A%40mail.gmail.com. >> For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to the Google Groups > "sympy" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sympy+unsubscr...@googlegroups.com. > To post to this group, send email to sympy@googlegroups.com. > Visit this group at http://groups.google.com/group/sympy. > To view this discussion on the web visit > https://groups.google.com/d/msgid/sympy/CAP7f1AiqsyHOQo%3Duy5pMNiqgriOhRrT%3DS18JO-uFTr%2BJUXC8-A%40mail.gmail.com. > > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "sympy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sympy+unsubscr...@googlegroups.com. To post to this group, send email to sympy@googlegroups.com. Visit this group at http://groups.google.com/group/sympy. To view this discussion on the web visit https://groups.google.com/d/msgid/sympy/CADDwiVDjgpvUJAREPZVWw1BTgPxhe9sYrfSt0zVsew%3DrhSJr1A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
