PGConf US PostgreSQL Power on Power. Michael Meskes. Bernd Helmle. Julian Schauder. credativ

Transcription

1 Michael Meskes Bernd Helmle Julian Schauder PostgreSQL Power on Power

2 Michael Meskes Free Software since 1993 Linux since 1994 Debian GNU/Linux since 1995 PostgreSQL since 1998

3 PostgreSQL since 2002 credativ since 2006 Performance High Availability Migration Bernd Helmle

4 PostgreSQL since 2012 Julian credativ since 2014 Schauder Performance High Availability Healthchecks

5 FOSS Specialists Complete Stack Supported All Major Open Source Projects Over 60 employees on staff Europe, North America, Asia Open Source Software Support and Services Support: break/fix, advanced administration, monitoring Consulting: selection, migration, implementation, integration, upgrade, performance, high availability, virtualization Development: enhancement, bug-fix, integration, backport, packaging Operating, Hosting, Training

6 Total Cost Software Hardware Training Downtime Staff Misc Of Ownership Source: IDC 2007

7 Use Case Commons Retailer Commons

8 PostgreSQL??? On Power

9 Direct seller since early 90ties Case Study Historical Early ecommerce adopter Historically growing IT infrastructure Success Story for PostgreSQL

10 IBM POWER since POWER5 introduction Case AIX and Linux OS platform Study IT Centralized IT server infrastructure Started with SLES10, but better support with RHEL

11 Two IBM S824 POWER8 machines (2 Sockets, 6 Cores, SMT-8 each) Case RHEL7 with PostgreSQL 9.4, inventory and logistics database instances have dedicated LPARs Study - Machines not colocated Certain transactions need guaranteed response times (+<n> ms) PostgreSQL Business logic in the database (Stored Procedures)

12 Architecture S824 S824 LPAR LPAR LPAR LPAR

13 Architecture

14 Corosync & Pacemaker ports from CentOS 7 Tasks Own builds because of SBD fencing Upstream SBD resource agent was part of this work PostgreSQL packages from PGDG optflags: ppc64 %{ global_cflags} -m64 -mcpu=power8 -mtune=power8./configure without-ldap...

15 Build infrastructure with Jenkins Package Build Infrastructure

16 Currently 48 logical CPUs (hardware threads) for logistics instance Performance Use huge pages hugepages=<n> kernel boot parameter, no transparent huge pages Stress tests show 10% more throughput (pgbench) Setup Use tuned to configure important system settings

17 Customized tuned configuration: Performance [main] include=throughput-performance [vm] transparent_hugepages=never Tuning [sysctl] kernel.sched_migration_cost_ns=

18 100 GByte RAM, shared_buffers = 10G Performance buffer reads buffer hits 24 hrs buffer stats

19 ~30GB transaction log traffic/day Manual CLUSTER and VACUUM FULL for certain tables Performance Standby lags during nightly batches

20 Performance ~1500 tps max ~800 tps average

21 Performance Very good system load Very cache centric (Latency!)

22 Backup Currently pg_dump only Dumps from streaming standby Queue tables are dumped in intervals (currently every 60min.) State tables are dumped daily and monthly Periodic archiving of data PITR planned for next setup iteration (Webshop migration)

23 Michael Meskes Bernd Helmle Julian Schauder PostgreSQL Power on Power