Performance Research - Simon Riggs - PGCon

More documents

Recommendations

Info

Availability “The customer must be able to access their data 24x7” No maintenance window Implies a reasonable response time -> steadiness 34 © 2007 EnterpriseDB Corporation
Availability: Recovery time Faster recovery with full_page_writes=on in 8.3 Future research: Reducing WAL size COPY performance (to speed up pg_restore) 35 © 2007 EnterpriseDB Corporation
Page 1 and 2: Enterprise Architecture & Performan
Page 3 and 4: Performance Features in PostgreSQL
Page 5 and 6: Web Site Database Single Applicati
Page 7 and 8: + Billing Business customers want
Page 9 and 10: + Decision Support Additional anal
Page 11 and 12: + Regulatory Archive Requirement f
Page 13 and 14: Workload Evolution (1) Generic pro
Page 15 and 16: Workload Evolution (3) Workload gr
Page 17 and 18: Enterprise Architect's Viewpoint H
Page 19 and 20: What is performance, and what can w
Page 21 and 22: Steadiness matters Benchmark of My
Page 23 and 24: Sources of unsteadiness: Vacuum Va
Page 25 and 26: Sources of unsteadiness: Other quer
Page 27 and 28: Throughput Performance Steadiness
Page 29 and 30: Adaptation “Can we run OLTP and
Page 31 and 32: Adaptation: Background Writer Auto
Page 33: Availability Performance Steadine
Page 37 and 38: Data Integration & DSS Performance

Performance Research - Simon Riggs - PGCon

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

Delete template?

Save as template?