[patch] default ForeignKey field results in terrible scaling perfomance
|Reported by:||Owned by:||Malcolm Tredinnick|
|Cc:||Triage Stage:||Design decision needed|
|Has patch:||yes||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
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
Change History (8)
comment:2 Changed 10 years ago by
|Summary:||default ForeignKey field results in terrible scaling perfomance → [patch] default ForeignKey field results in terrible scaling perfomance|
|Version:||0.95 → SVN|