These are instructions on setting up your worker for the PostgreSQL Performance Farm. The worker is a Buildbot worker that needs to be configured and setup for the PostgreSQL Performance Farm.
The worker does its thing primarily in its own directory. Thus it is currently limited to using only the storage it is residing on.
In addition to installing the files in this repository, additional software may be needed for each of the following tests. See the following section for each test that this worker intends to run for more details.
DBT-2 is a fair-use implementation of the TPC Benchmark(TM) C. No additional files are need to run this test.
DBT-3 is a fair-use implementation of the TPC Benchmark(TM) H. The TPC-H Tools must be downloaded by you or your organization. Create a subdirectory dbgen at the top level this repository and unzip the tools into that subdirectory. Follow the section Building TPC-H Tools on how to download compile the tools.
DBT-5 is a fair-use implementation of the TPC Benchmark(TM) E. The TPC-E Tools must be downloaded by you or your organization. Create a subdirectory egen at the top level this repository and unzip the tools into that subdirectory. Follow the section Building TPC-E Tools on how to download compile the tools.
DBT-7 is a fair-use implementation of the TPC Benchmark(TM) DS. The TPC-DS Tools must be downloaded by you or your organization. Create a subdirectory dsgen at the top level this repository and unzip the tools into that subdirectory. Follow the section Building TPC-DS Tools on how to download compile the tools.
Put your name and email address into the info/admin file.
Put a description of the server into the info/host file. An example of what to put is coming...
Copy settings.py.sample to settings.py and update the WORKERNAME and SECRET accordingly.
Different hardware probably should have PostgreSQL configured differently, and each test probably needs further configuration changes. So each worker is able to have its own set of configuration files that will added to PostgreSQL. To accommodate all the different combinations, first create a subdirectory guc and create files with name in the format $TEST.$BRANCH.conf.
For example, to create files for custom PostgreSQL configuration settings for DBT-2 that will be used in the master and v16 branches, create the following two files:
mkdir guc touch dbt2.master.conf touch dbt2.REL_16_BRANCH.conf
The format of the files is the same as the postgresql.conf file. For example, to change a couple parameters:
checkpoint_timeout = 30min max_wal_size = 1000GB