Not sure if this is a Django issue or the supporting Mysqldb (1.2.2)
python package .. (i'll stop this here if its not, but it seems worthy
of at least letting other know this)
however while profiling a page i came across this seemingly
performance hole.
--------
Ordered by: internal time
ncalls tottime percall cumtime percall
filename:lineno(function)
230 0.343 0.001 0.343 0.001 {method 'query' of
'_mysql.connection' objects}
228 0.116 0.001 0.116 0.001 {method 'ping' of
'_mysql.connection' objects}
234 0.029 0.000 0.047 0.000 query.py:
473(get_default_columns)
972 0.021 0.000 0.048 0.000 __init__.py:
487(__init__)
1303 0.019 0.000 0.022 0.000 __init__.py:
633(__init__)
2068 0.017 0.000 0.216 0.000 __init__.py:
690(_resolve_lookup)
-------
#1 time sink is the queries themselves (i figured that would be the
case) .. but #2 is "ping" and it seems to ping on every query. This
issue is probably not so bad on Localhost or Socket based connections,
but on remote Mysql server, as you can see, it is not so good.
again not sure if django can solve (or even wants to solve this) ..
bo
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
