Successful MySQL Scalability
Upcoming SlideShare
Loading in...5
×
 

Successful MySQL Scalability

on

  • 6,495 views

 

Statistics

Views

Total Views
6,495
Views on SlideShare
4,990
Embed Views
1,505

Actions

Likes
8
Downloads
289
Comments
0

7 Embeds 1,505

http://ronaldbradford.com 1478
http://www.scoop.it 11
http://translate.googleusercontent.com 10
http://static.slidesharecdn.com 3
http://webcache.googleusercontent.com 1
http://www.linkedin.com 1
http://ranksit.com 1
More...

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Successful MySQL Scalability Successful MySQL Scalability Presentation Transcript

  • Successful MySQL Scalability 2010.08 Ronald Bradford www.RonaldBradford.com @RonaldBradford #mysql
  • The one hour version
  • OUTLINE Necessary Principles System Architecture Data Availability Best Practices Being proactive Successful MySQL Scalability
  • 1 Successful MySQL Scalability
  • Action Integrated monitoring and instrumentation Successful MySQL Scalability
  • EXAMPLE Question: ✘ How do you know when your server is down or not accessible? Answer: The users will let us know. Successful MySQL Scalability
  • How Monitoring/Alerting Graphical Historical Necessary Generally missing/incomplete Useless for real-time analysis Successful MySQL Scalability
  • How Monitoring/Alerting TIV E C Graphical R E A Historical Necessary Generally missing/incomplete Useless for real-time analysis Successful MySQL Scalability
  • How Dashboard The state of NOW Sampling at 1s/3s/5s e.g. 0.1% of throughput http://rb42.com/monitoring-needs Successful MySQL Scalability
  • How Dashboard T I V E OAC The state of NOW P R Sampling at 1s/3s/5s e.g. 0.1% of throughput http://rb42.com/monitoring-needs Successful MySQL Scalability
  • How Instrumentation Important to business viability e.g. orders per minute (KPI) page load time Seamless implementation i.e. no code changes to view real-time extensible Successful MySQL Scalability
  • How Instrumentation T I V E OAC Important to business viability R e.g. orders per minute (KPI) P page load time Seamless implementation i.e. no code changes to view real-time extensible Successful MySQL Scalability
  • WHY Monitoring + Instrumentation = Preemptive Analysis Successful MySQL Scalability
  • How ✘ Successful MySQL Scalability
  • How ✔ < 1 second Successful MySQL Scalability
  • WHY Preemptive Analysis Fail early Faster user response Less physical resource impact Successful MySQL Scalability
  • TIP Have a status website allow for comments (e.g. blog) Have a public dashboard website Host them somewhere else! Successful MySQL Scalability
  • 2 Successful MySQL Scalability
  • Action Seamless automated server deployment Successful MySQL Scalability
  • Example Actual Client 100+ production database servers ✘ Full-time DBAs No automated software installation No single documented installation process No version control No auditing/verification Successful MySQL Scalability
  • How Basics Version Control Automated Build & Release Integrated Monitoring Successful MySQL Scalability
  • How Intermediate Health Checks Runtime config file management Benchmarking Successful MySQL Scalability
  • How Advanced Server request queue Automated discovery Proactive scaling (up & down) Successful MySQL Scalability
  • GOAL Consistent and timely provisioning Unattended installation with correct and reproducible ✔ configuration Automated discovery Successful MySQL Scalability
  • 3 Successful MySQL Scalability
  • Action Disaster is inevitable Successful MySQL Scalability
  • Example Question: ✘ Have you ever performed a database recovery? Answer: No, why? Successful MySQL Scalability
  • Example Consultant: ✘ Do you know that your daily backups only recover the data up to that time (e.g. 1 am). You know you have lost all your sales and data changes since then. Customer: No, I didn’t know that. Successful MySQL Scalability
  • HOW Have a DR plan Documented Tested Timed Verified Successful MySQL Scalability
  • HOW Test under production conditions System Load Database Size End to End Successful MySQL Scalability
  • GOAL Know and practice for disaster Provide confidence to management ✔ Be as confident about your recovery as your scalability Successful MySQL Scalability
  • SIDEBAR! What does your website look like when it’s down? Successful MySQL Scalability
  • SIDEBAR! ✘ Google Picasa Successful MySQL Scalability
  • SIDEBAR! ✘ Successful MySQL Scalability
  • SIDEBAR! ✘ Mozilla Successful MySQL Scalability
  • SIDEBAR! ✔ Successful MySQL Scalability
  • SIDEBAR! ✔ Successful MySQL Scalability
  • 4 Successful MySQL Scalability
  • Action Application Programming Interface Successful MySQL Scalability
  • Example Public API ✘ Application web site Batch processes 3 access paths to same data with different business rules Successful MySQL Scalability
  • Why One code path for business functionality Implied business documentation Enforced data exchange standard Testability Successful MySQL Scalability
  • GOAL Technology independence Business specification dependence (API) ✔ Stress testable Successful MySQL Scalability
  • SIDEBAR! Testing is not about what works, it’s about breaking your software Successful MySQL Scalability
  • 5 Successful MySQL Scalability
  • Action Support different levels of data availability Successful MySQL Scalability
  • HOW Data can be: Read & Write Read No Access Cached Successful MySQL Scalability
  • EXAMPLE Development Team: We need a maintenance window for software upgrades and new releases. Successful MySQL Scalability
  • EXAMPLE Management Team: No Downtime Successful MySQL Scalability
  • EXAMPLE Development Team: But we need this to fix problems and improve performance. Successful MySQL Scalability
  • EXAMPLE Management Team: No Downtime Successful MySQL Scalability
  • EXAMPLE What is your definition of no downtime? Successful MySQL Scalability
  • WHY Support downtime Software upgrades Support disasters Reduce high load Support partial functionality Successful MySQL Scalability
  • GOAL Meet the business needs of availability ✔ There are ways to give greater perception of availability Successful MySQL Scalability
  • 6 Successful MySQL Scalability
  • Action Support different scalability principles Successful MySQL Scalability
  • HOW Read Scalability Write Scalability Caching Successful MySQL Scalability
  • HOW Depends on your R/W ratio Depends on your business needs Depends on rate of data change (caching) Successful MySQL Scalability
  • ISSUES Consistency Data Interoperability Successful MySQL Scalability
  • GOAL ✔ Support large scale growth with appropriate software architecture Minimize human interaction Ongoing review and improvement Successful MySQL Scalability
  • SIDEBAR! Availability options & scalability principles = scalable datastore Successful MySQL Scalability
  • 7 Successful MySQL Scalability
  • What’s NEXT I only had one hour! Successful MySQL Scalability
  • What’s NEXT Reduce deployment time The right business metrics Team dynamics Managing risk Continual improvement Asynchronous Data interoperability Write once data ... Consistency Successful MySQL Scalability
  • R Successful MySQL Scalability
  • RECAP Monitoring. Before, during and after NOW. You may not be able to predict the future but you can preempt the future. Operate below 90%. That 10% is your insurance policy. Invest in insurance. Successful MySQL Scalability
  • RECAP Does your business exist without your data? How long can your site be unavailable before customers go elsewhere? Successful MySQL Scalability
  • RECAP Support 3 levels of real time data access Read/Write, Read and no access Support 3 different aspects of scalability Read, Write and Caching Successful MySQL Scalability
  • RECAP If you can’t drive without a mouse, find somebody that can. Successful MySQL Scalability
  • Reference The most common MySQL scalability mistakes, and how to avoid them. http://omniti.com/surge Successful MySQL Scalability
  • Reference ‣ 1. My website is slow? ‣ 2. I want to add new H/W. How do I change my application to support this? ‣ 3. The database is slow. My webpage takes five seconds to load. ‣ 4. Why is my database executing so many qps? Successful MySQL Scalability
  • Reference ‣ 5. My server has crashed with a hard drive failure ‣ 6. My replication slave can't keep up? ‣ 7. I can't access my website? ‣ 8. Why is my database so large? ‣ 9. My website seems to freeze or responds randomly? Successful MySQL Scalability
  • CONFERENCES MySQL Sunday O'Reilly MySQL Conference 2011 Colloborate 2011 Kaleidoscope (KScope) 2011 http://ronaldbradford.com/blog/2011-mysql-conferences-2010-09-07/ Successful MySQL Scalability
  • CONTACT http://ronaldbradford.com me@ronaldbradford.com Successful MySQL Scalability Successful MySQL Scalability