#5513: Last session refactoring vastly down Django performance
------------------------------------+---------------------------------------
Reporter: msaelices | Owner: msaelices
Status: assigned | Component: Contrib apps
Version: SVN | Resolution:
Keywords: slowness performance | Stage: Unreviewed
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
------------------------------------+---------------------------------------
Comment (by msaelices):
I think ticket is fixed with this patch. The problem was:
* Before [6333]: {{{session_key}}} attribute of {{{SessionWrapper}}}
object, was only a python attribute
* After [6333]: {{{session_key}}} attribute of {{{SessionBase}}} object
(the same class after refactoring), is a python property, defined as:
{{{
#!python
session_key = property(_get_session_key, _set_session_key)
}}}
Every access to {{{self.session_key}}} check is there is a session and
creates one if not. But in code patched, i ask for session_key attribute,
not for session_key in DB.
--
Ticket URL: <http://code.djangoproject.com/ticket/5513#comment:10>
Django Code <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 [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?hl=en
-~----------~----~----~----~------~----~------~--~---
