On Wed, Sep 10, 2008 at 5:33 AM, Eduardo O. Padoan <[EMAIL PROTECTED]> wrote: > 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.
Actually, this is precisely what I *don't* want out of a Django benchmark. It's nearly impossible to benchmark two totally different stacks of software against each other, and unless you're *perfect* the results are meaningless. On top of that, I don't particularly care how well we compare against other frameworks -- we're both "fast enough" -- but I care *highly* how Django trends over time. Jacob --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
