#17291: Oracle: cache the server version when first needed
----------------------------------------------+--------------------
Reporter: akaariai | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Database layer (models, ORM) | Version:
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 1
Easy pickings: 0 | UI/UX: 0
----------------------------------------------+--------------------
As discussed in [http://groups.google.com/group/django-
developers/browse_thread/thread/490d0f96db7f7f43 this] django-developers
thread, it would be good from performance standpoint to cache the version
information when first needed, and then use that information for every
connection taken from that DB. The caching is per database alias.
There is also some cleanups included in the patch. The main thing is that
I added supports_regex `DatabaseFeature`, which is false for Oracle v9.
The attached patch does pass lookup tests. It is about 20% faster on
taking 1000 connections and immediately closing them.
I do get one test failure in basic tests, but I do get the same failure in
test_unicode_data on master, too. Probably something wrong with my setup.
I am running the full test suite currently, but I can't report about
results until Monday when I am next at work.
Unfortunately I can't test this on Oracle v9.
--
Ticket URL: <https://code.djangoproject.com/ticket/17291>
Django <https://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.
