Performance Research - Simon Riggs - PGCon

More documents

Recommendations

Info

IT Manager's Viewpoint We mustn't ever lose our critical data The customer must be able to access their data 24x7 It must be cheap in the long term, not just at the start I want it to perform well The decision to use PostgreSQL must be low risk. I'm not going to let technical favouritism get in the way of my job. 18 © 2007 EnterpriseDB Corporation
What is performance, and what can we hackers do about? “I want it to perform well” <strong>Performance</strong> Steadiness Throughput Adaptation “It must be low-risk” -> Scalability 19 © 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: Enterprise Architect's Viewpoint H
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

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

Delete template?

Save as template?