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
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
I think one very important feature is submitting results back to
djangoproject.com for comparison. Since Django is so dependent on
underlying components it'll be very hard to compare results, but at
the very least we can track things like:
CPU type and speed
python version
memory (installed, free
On Sep 10, 12:24 am, "Jeremy Dunck" <[EMAIL PROTECTED]> wrote:
> OK, enough noise on the naming.
(I really like metronome)
> 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 t
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
