On Sunday, September 15, 2013 3:13:09 AM UTC+3, Curtis Maloney wrote: > > Hey, thanks for that! > > It would be nice to have something that would chart this over time... > something like some people have set up for GCC. > > I've never been able to get djangobench to give meaningful results, > otherwise I'd do it. > > Mmm... perhaps I've just found a use for my odroid :) >
I have a simple setup for generating graphs over time. Results are something like this: http://users.tkk.fi/~akaariai/djbench/model_save/. Unfortunately I haven't found the time to automate benchmarking. When using djangobench it is extremely important to turn all sorts of cpu speed throttling off. Power saving features will cause random results. It seems the older your hardware is, the better results you will get. Even then, if you forget to disable cpu throttling you will get results like this: http://users.tkk.fi/~akaariai/djbench/model_creation/ I managed to spot why form_create is 15x slower in average - it is all about translation startup speed. A string that wasn't translatable before now is, and I guess the first time that string is translated will cause a huge spike in runtime. Luckily the rest of iterations are about same as always. In short, form_create was a false alarm. Or, see http://users.tkk.fi/~akaariai/djbench/form_create/ - Anssi -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. For more options, visit https://groups.google.com/groups/opt_out.
