News for hackers. Stuff that matters.
Re:Don't test with SQLite when you use Postgres in Production by mgamer on Tuesday August 04, 2015 @05:44AM (#10002404)
I use MySQL in my system but the advice should be applicable to Postgres as well: keep your test database in a ramdisk. By moving my MySQL to ramdisk I got almost a tenfold improvement when running tests on a build server. Not so much (but also significant) improvement when running tests on my development machine.
Re:Don't test with SQLite when you use Postgres in Production by jeltz on Tuesday August 04, 2015 @08:19AM (#10002862)
We have benchmarked this at our company and notivced that using a ramdisk does not give much extra performance over just turning of synchronous_commit in PostgreSQL. Most of the slowdown from the database turned out to be latency from waiting on the background writer to fsync.
Re:Don't test with SQLite when you use Postgres in Production by jackweirdy on Tuesday August 04, 2015 @05:57AM (#10002439)
Why do you think there was a difference between tests on a build server and on your development machine? Was it just a case of the build server being configured for performance?
Re:Don't test with SQLite when you use Postgres in Production by mgamer on Tuesday August 04, 2015 @06:11AM (#10002471)
I'm pretty sure that it's down to hard disk performance. I don't recall exact numbers but difference in IOPS between my development machine and a build server in the cloud (Azure) was greatly in favour of the former.