The main historical problem with pgbench is that the results it generates are not particularly consistant from run to run. The approach taken here to cope with that is to run each test many times, with significantly more transactions than are normally used, then average the results out. pgbench-tools used for background writer testing This software was used to test various background writer methods as part of trying to improve the LRU cleaner in the upcoming 8.3 release of PostgreSQL. The results are available. I haven't found anything better than pgbench for generating write workloads guaranteed to completely fill whatever I/O subsystem you have. The first problem is that you still have to size the database appropriately to keep seek behavior from dominating test results. Shared_buffers | 32768 (=256MB) wal_sync_method | open_sync checkpoint_segments | 32 wal_buffers | 128 autovacuum | off. Tests de régression PostgreSQL. Les tests de régression composent un ensemble exhaustif de tests pour l'implémentation SQL dans PostgreSQL™.

Furthermore, they implement important functionality in the form of database methods (stored procedures, stored functions, and/or triggers) and database objects (e.g. Java or C# instances). The best way to ensure the continuing quality of these assets, at least from a technical point of view, you should have a full regression test suite which you can run on a regular basis. In this article I argue for a fully automated, continuous regression testing based approach to database testing. Just as agile software developers take this approach to their application code, see Agile Testing and Quality Strategies, we should also do the same for our databases.

The PostgreSQL Performance lab is being created to allow community members of the Open Source database PostgreSQL to have enterprise class hardware to test on. The testing that will occur includes industry standard workloads such as OLTP, DSS and BI. Furthermore we will also use the hardware for other practical and customer oriented testing to improve scalability (processor utilization, i/o, load balancing, etc.) and managing large data sets (loading, backups, restores, replication, etc). Donations For donation inquiries, please contact Josh Berkus <josh @t postgresql.org> and Joshua Drake <jdrake @t postgresql.org>.

Mailing List There is a mailing list available to discuss administrative aspects of community equipment. QA platforms Tools Ideas look into sysbench - it has some issues with locking on postgresql but at least read-only it seems to work fine. Datasets. Tsung. JMeter.