#15119: MySQL backend generates unnecessary commands
-------------------------------------+--------------------------------------
Reporter: lukesneeringer | Owner: nobody
Status: new | Milestone:
Component: Uncategorized | Version: 1.2
Resolution: | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-------------------------------------+--------------------------------------
Changes (by ramiro):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
IMHO, if it is in Django hands to optimize this (i.e. there is some
MySQLdb knob or DP-API complaint change of workflow in query generation
that would help in reducing that `com_admin_command` counter) then it
would be worth considering. But to even start thinking about this we need
more concrete information, real numbers about the overhead introduced
compared to real data in-band traffic. ''Probably a pretty small amount of
overhead, but it definitely seems like a waste'' is going to get the same
traction as the thread you pointed got. Karen asked for this same
information to the OP there and there was no answer.
Fortunately, it seem you have a dedicated MySQL DBA fellow that can give
you and us that information. Can you coordinate collecting some valuable
data?
--
Ticket URL: <http://code.djangoproject.com/ticket/15119#comment:1>
Django <http://code.djangoproject.com/>
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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
