The test was performed using the venerable pgbench tool that comes bundled with PostgreSQL. To replicate a typical production setup, the disks utilized LUKS full-disk encryption and WAL archiving was enabled to include the overhead of backups in the tests.
![aws postgresql data science aws postgresql data science](https://miro.medium.com/max/1400/0*0CXzkVL2ddgbYdES.png)
PostgreSQL 10.0 was running on top of Linux 4.3.15 kernel on each cloud. 350 GB gp2 EBS volume, no provisioned IOPS.4 vCPU / 16 GB RAM network disks benchmarkĪlthough it is impossible to get VMs with the exact same specifications in every cloud, we provisioned similar setups in all clouds: The second compared network and local SSD performance in AWS and GCP cloud infrastructures with the same instance sizes as the first.įor this post, we will be taking an in-depth look at the two benchmark tests while covering some important considerations when identifying and correcting PostgreSQL setups. The first benchmark was compared the following two different instance sizes on all clouds utilizing the network-backed freely scalable disks that are available in each cloud: We selected the specific regions because we were giving the talk a European conference and all of the vendors operate data centers in England and Germany.Īlso, chose to run all benchmarks in two different regions to see if we would find noticeable differences in the different sites operated by these vendors. Microsoft Azure (UK South and Germany Central).Google Cloud Platform (europe-west2 and europe-west3).Amazon Web Services (eu-west-1 and eu-central-1).The talk compared the results of 3 benchmark tests for the just released PostgreSQL 10 running in five cloud infrastructures in two different regions: I recently gave a talk about PostgreSQL performance in different clouds, under different settings at the conference in Warsaw.