Your SlideShare is downloading. ×
0
where is your data cached?
where is your data cached?
where is your data cached?
where is your data cached?
where is your data cached?
where is your data cached?
where is your data cached?
where is your data cached?
where is your data cached?
where is your data cached?
where is your data cached?
where is your data cached?
where is your data cached?
where is your data cached?
where is your data cached?
where is your data cached?
where is your data cached?
where is your data cached?
where is your data cached?
where is your data cached?
where is your data cached?
where is your data cached?
where is your data cached?
where is your data cached?
where is your data cached?
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

where is your data cached?

844

Published on

Taking a look at the many layers of caching in the modern webstack can lead to some interesting optimizations. We know that raid card caches, disk caches and CPU caches all exist at the hardware …

Taking a look at the many layers of caching in the modern webstack can lead to some interesting optimizations. We know that raid card caches, disk caches and CPU caches all exist at the hardware level, but how do they interact with database caching, application code caching and rendered page caching. Where are the redundancies and where is the most optimal location for your services to cache? Are you risking data integrity by using both disk and raid card caching? Is there a similar risk in using both filesystem and database caching? These are hard won lessons if you have to learn them during an outage. they can be avoided with some forethought and benchmarking. I’ll call out the many layers where data is cached and talk about some of the risks and potential performance gains that we’ve found by selectively disabling and adding particular caching layers.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
844
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
9
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • fundamentally we cache to improve speed. that’s accomplished by moving data to the furthest out point in a architecture that it can safely reside. pushing that data out as close to the client as possible.
  • how many caching points do you think there are in a modern web stack? I’m sure I’ve missed some that happen but I counted 9 that I see in most architectures.
  • client side once I’ve expanded the hardware caching again I count 6.
  • Choose 5.1 or 5.4 only if you need the featuresets.
  • Choose 5.1 or 5.4 only if you need the featuresets.
  • Choose 5.1 or 5.4 only if you need the featuresets.
  • Choose 5.1 or 5.4 only if you need the featuresets.
  • Choose 5.1 or 5.4 only if you need the featuresets.
  • Choose 5.1 or 5.4 only if you need the featuresets.
  • •❑ disk•❑memory•❑up/down•❑cachehit -- baseline defiinition•❑replication •❑ mktablesync•❑mkchecksum
  • Transcript

    • 1. where is your data cached? (and where should it be cached?) sarah novotny [email_address]
    • 2.
      • why do we cache?
      • count them
      • which are redundant?
      • which are a risk?
      • benchmarking
      • monitoring
    • 3.
      • why do we cache
      cache: a component that transparently stores data so that future requests for that data can be served faster
    • 4.
      • count them
      CPU caches (L1, L2, L3) disk caches disk controller caches database caches memcached layer application code caches http cache edge cache or CDN operating system caches
    • 5. and then there were more DNS caching (ISP and client side) web proxies client side application caches and all the hardware caching again
    • 6.
      • a short diversion:
      my background is as an SA and DBA. i’ll be focusing data safety facets of caching
    • 7.  
    • 8. disk caches disk controller caches database caches memcached layer operating system caches
    • 9.
      • which are redundant?
    • 10. get moving!
    • 11.  
    • 12.
      • which are a risk?
    • 13. disks lie
    • 14. raid controllers lie (sometimes)
    • 15.  
    • 16.
      • benchmarking
    • 17.  
    • 18. every infrastructure is different every benchmark has to take that into account
    • 19.  
    • 20.
      • monitoring
    • 21. measure multiple points only you can prevent firedrills
    • 22.  
    • 23.
      • tools to manage
      • this insanity—
      • Innotop
      • Percona toolkit
      • sysbench
      • cacti templates
      • nagios
    • 24. credits
      • flickr
      • license plate – severud
      • tools – meanestindian
      • other
      • 3ware image via http:// www.xbitlabs.com /
      • remaining images istockphoto
    • 25. CIO Meteor Entertainment Program Chair OSCON Program Chair PLMCE Board Member Blue Gecko Chef Community MySQL Community [email_address] @sarahnovotny stuff I do

    ×