PostgreSQL Performance From the Ground Up

Recommendations

Info

● listen_addresses PostgreSQL, Cont. ● Listen on as few interfaces as possible. Connections are expensive. ● Filter at the firewall level instead, so there is less of a chance of a DDOS on your DB. ● Make lots of use of the pg_hba.conf
● max_connections = 100 PostgreSQL, cont. ● Default. Connections take memory and processing to set up and tear down. ● Use a connection pooler to handle more connections and to keep them persistent. ● Pgbouncer and pgpool are good choices
Page 1 and 2: PostgreSQL Performance From the Gro
Page 3 and 4: Choosing Hardware ● These are nic
Page 5 and 6: Hardware Basics: Memory ● Rule of
Page 7 and 8: Hardware Basics: Memory, Cont Funct
Page 9 and 10: Hardware Basics: Disks, cont. ● R
Page 11 and 12: Hardware Basics: Disks, Cont Rotati
Page 13 and 14: ● dd Hardware Basics: Disks, Cont
Page 15 and 16: Operating System, Cont. ● Ext3 da
Page 17 and 18: Operating System, Cont. ● vm.dirt
Page 19 and 20: Operating System, Cont. ● Use tab
Page 21 and 22: PostgreSQL ● shared_buffers make
Page 23: ● effective_cache_size ● 50-75%
Page 27 and 28: PostgreSQL, Cont. ● effective_io_
Page 29 and 30: PostgreSQL, Cont. ● checkpoint_ti
Page 31 and 32: ● Don't change these: PostgreSQL,
Page 33 and 34: PostgreSQL, Cont. ● Autovacuum Co
Page 35 and 36: PostgreSQL, Cont. ● Autovacuum is
Page 37 and 38: ● log_rotation_age = 1d ● log_r
Page 39 and 40: Queries, Cont. lacey@[local]:5432:l
Page 41 and 42: Queries, Cont. ● Biggest query is

PostgreSQL Performance From the Ground Up

Create successful ePaper yourself

Delete template?

Save as template?