#5203: Performance improvement for sqlite3 database flush
------------------------------------+---------------------------------------
   Reporter:  [EMAIL PROTECTED]  |                Owner:  nobody          
     Status:  new                   |            Component:  Database wrapper
    Version:  SVN                   |           Resolution:                  
   Keywords:  sqlite performance    |                Stage:  Accepted        
  Has_patch:  1                     |           Needs_docs:  0               
Needs_tests:  0                     |   Needs_better_patch:  0               
------------------------------------+---------------------------------------
Comment (by [EMAIL PROTECTED]):

 >>I just tried applying the patch and running the Django system tests
 (which does plenty of flushing). I saw no improvement - certainly not a 3x
 speedup.

 I expect the big improvements when flushing bigger/'production-size'
 databases: the database file will have plenty of database 'pages' and
 waiting for disk io will be the clear bottleneck. In smaller databases
 other bottlenecks can more easily pop up.

 To prove the speedup, some for-loop can be used to populate the database
 with a sufficient number of records. Flushing that database with and
 without the patch will demonstrate the improvement...

-- 
Ticket URL: <http://code.djangoproject.com/ticket/5203#comment:11>
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to