<html> <head> <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> On 10/24/2011 03:32 PM, Lukas Zapletal wrote: <blockquote cite="mid:4EA568DC.1070103@redhat.com" type="cite">Hey, since we started using PostgreSQL for our unit tests I did some quick-googling today and found this postgresql.conf setting: # tail /var/lib/pgsql/data/postgresql.conf fsync=off synchronous_commit=off full_page_writes=off bgwriter_lru_maxpages=0 Those four lines will set your database instance to highly asynchronous mode, that means everything is much faster (no synchronized hdd writes - my hdd LED literally does not blink during whole test). While this improves database performance a lot, it can cause loss of data in case of power outage. Please DO NOT use this for production systems :-) I did not do any measurements but unit test run is notable faster. Feel free to share your numbers. </blockquote> Cool. This is output from my testing: Without this settings: 1075 examples, 0 failures, 20 pending real 4m35.818s user 3m29.188s sys 0m7.560s one spec file: real 0m18.987s user 0m10.995s sys 0m1.894s <big> </big>With this settings: real 4m39.068s user 3m34.858s sys 0m7.772s one spec file: real 0m14.200s user 0m10.897s sys 0m1.893s It's faster when running few tests (e.g. a single spec file) - faster preparation of the database. There is no difference for the whole test suite. However, this measurement doesn't include the saving of the disk. -- Ivan </body> </html>