PostgreSQL Performance From the Ground Up

Recommendations

Info

Operating System, Cont. ● kernel.shmall = PAGE_SIZE / 2 ● kernel.shmmax = kernel.shmall * PAGE_SIZE ● Good estimates of changing shared memory sizes.
<strong>PostgreSQL</strong> ● shared_buffers make <strong>the</strong> most difference. They consist of: 1. Connections/Autovacuum Workers. 2. Prepared transactions 3. Shared Disk Buffers* 4. Wal Buffers 5. Fixed Space.
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: Operating System, Cont. ● Use tab
Page 23 and 24: ● effective_cache_size ● 50-75%
Page 25 and 26: ● max_connections = 100 PostgreSQ
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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?