#8138: Switch django tests to use transactions
----------------------------------------+-----------------------------------
Reporter: mremolt | Owner: nobody
Status: closed | Milestone: post-1.0
Component: Testing framework | Version: SVN
Resolution: fixed | Keywords:
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
----------------------------------------+-----------------------------------
Comment (by MockSoul):
fcuk!
notice that sqlite3 + :memory: + dont flush at all (use fork() for each
test, it will entirely copy in-memory sqlite3 database) -- fastest way to
run tests. [br]
My personal stats (quad core) (my own app test, not django):
1. postgresql+transactions: 600sec
2. mysql-innodb+transactions: 450sec
3. mysql-myisam: 700sec
4. sqlite3-inmemory-forkhack: 180sec (!)
5. sqlite3-inmemory-traditional: 400sec (a lot of time for flushing)
6. postgresql+transacitons: 15 minutes and counting.. :))
--
Ticket URL: <http://code.djangoproject.com/ticket/8138#comment:34>
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
-~----------~----~----~----~------~----~------~--~---
