#2638: default ForeignKey field results in terrible scaling perfomance
---------------------------+------------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: adrian
Type: defect | Status: new
Priority: normal | Milestone:
Component: Validators | Version: 0.95
Severity: critical | Keywords:
---------------------------+------------------------------------------------
Normally I'm not sure I'd call this a defect, but the default values for
models.ForiegnKey (specifically raw_admin_id) have such a negative
performance impact that I couldn't avoid it.
The discussion on the django-user's mailing list at
http://groups.google.com/group/django-
users/browse_thread/thread/ca0640e1cd0149a4/484695e3983c1858?lnk=gst&q=AddManipulator+performance&rnum=1#484695e3983c1858
caught my attention.
While I really like the behavior that's enabled without raw_admin_id, I
think the default value should favor the scaling/performance side of
Django, with the additional functionality of returning potential values
from the validator being the opt in.
I've posted the test case code I used at
http://www.rhonabwy.com/django_perf_test.zip
--
Ticket URL: <http://code.djangoproject.com/ticket/2638>
Django <http://code.djangoproject.org/>
The web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" 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-updates
-~----------~----~----~----~------~----~------~--~---
