On Tue, Sep 9, 2008 at 8:24 PM, Jeremy Dunck <[EMAIL PROTECTED]> wrote: > > OK, enough noise on the naming. > > Let's talk about what it should be and what should be measured. :) > (I suspect some devs already have a sketch regarding this stuff. > Please share.) > > Do we want it to result in one big number like python/Lib/test/pystone.py? > > Do we want to provide hooks for apps to supply something to stones for > site-specific stone testing? > > Measuring: > * loading > * hello world request cycle > * template parsing > * template rendering > * generic views(?) > * various query mashing (repeated filters, combination, negation, count) > * signaling > * form validation > * cache > * model instantiation/save > * various laziness > * utils (encoding, datastructures > > What else?
It'll need benchmark to test the number of requests per second that we can process, something that could be used to test other frameworks too, so we can compare Django's performance to, e.g., Turbogear's. > Also, what about things that affect downstream performance, but don't > affect our runtime, like the HTTP Vary header? -- Eduardo de Oliveira Padoan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
