On Mon, Sep 22, [EMAIL PROTECTED] wrote: > Django with #3460 is _significantly_ faster when the query load is > high. If I ran stock Django on Chesspark, the database overhead would > cripple the site.
I'd really like to see a kind of benchmark that I can try out to check your measurements. A previous poster found your claims to be not justified. I'm very curious were the overhead comes from. The database more or less needs to use transactions internally anyway, even for a select, to give you a consistent view for a select. It cannot know that you get only one (1) result. So, is the overhead just from parsing the transaction statements? Michael -- noris network AG - Deutschherrnstraße 15-19 - D-90429 Nürnberg - Tel +49-911-9352-0 - Fax +49-911-9352-100 http://www.noris.de - The IT-Outsourcing Company Vorstand: Ingo Kraupa (Vorsitzender), Joachim Astel, Hansjochen Klenk - Vorsitzender des Aufsichtsrats: Stefan Schnabel - AG Nürnberg HRB 17689 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
