Well, Jeremy Dunck was kind enough to do a benchmark against the old
system: 
http://groups.google.com/group/django-developers/browse_thread/thread/815f76ad7e823cbf/b008a757fbdefa2b



On Nov 16, 9:49 pm, "Russell Keith-Magee" <[EMAIL PROTECTED]>
wrote:
> On Mon, Nov 17, 2008 at 11:20 AM, Malcolm Tredinnick
>
>
>
> <[EMAIL PROTECTED]> wrote:
>
> > On Sun, 2008-11-16 at 18:11 -0800, [EMAIL PROTECTED] wrote:
> >> In terms of signal overhead, the most likely case here is probably no
> >> receivers, and in the signal refactor, that particular case is now
> >> hugely faster.
>
> > "Hugely" being, of course, a highly scientific measurement lending
> > itself to accurate comparison against future changes. :-)
>
> > Yes, I know it's faster now and I realise that's the common case. But
> > what's the impact of adding one or two new signal calls per request. I
> > suspect it's minimal, but I haven't measured it and this is the first
> > time it's come up since the refactor, so it's probably time to know what
> > we're agreeing to for each new signal.
>
> This sort of benchmarking would be helpful to have kicking around. One
> of the features on the table for v1.1 is to add signals for activity
> on m2m operations. The biggest impediment to introducing these signals
> is the overhead (or, at least, the perception that there will be an
> overhead) associated with adding a signal for a common operation.
>
> I would like to see m2m signals introduced (overhead permitting), so
> I'll probably have to work up a set of benchmarks at some point so
> that we can have the debate over some concrete numbers rather than
> perceptions and speculation. If someone else were to save me the
> effort of having to write these benchmarks myself, I would buy them a
> lollipop* :-)
>
> Russ Magee %-)
>
> * Lollipop offer valid while stocks last. ISO standard size and
> flavor. Offer void where prohibited.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to