Performance Research - Simon Riggs - PGCon

More documents

Recommendations

Info

Workload Evolution (4) Workload separated Typical Responses “Best way to transfer data?” “How can we keep them as current as possible?” “How to reduce the impact on the source system?” “How to change the data model as we move the data?” “How can we speed up endto-end load process?” 16 © 2007 EnterpriseDB Corporation
Enterprise Architect's Viewpoint How can I maintain continuous access to data via web site? How can offer a worthwhile Service Level Agreement? How can I do that as the business grows? Can I consolidate my servers? How do I mix workloads for as long as possible? How do I approach data integration between servers? How can I increase the number of decision support queries the business runs each month? How can I mix long term archive with shorter term decision support requirements? 17 © 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: Workload Evolution (3) Workload gr
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 and 34: Availability Performance Steadine
Page 35 and 36: Availability: Recovery time Faster
Page 37 and 38: Data Integration & DSS Performance

Performance Research - Simon Riggs - PGCon

Create successful ePaper yourself

Delete template?

Save as template?