where is your data cached?

(and where should it be cached?)

sarah novotnysarah.novotny@gmail.com

①why do we cache?②count them③which are redundant?④which are a risk?⑤benchmarking ⑥monitoring

①why do we cache

cache: a component that transparently stores data so that future requests for that data can be served faster

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

② count them

and then there were more

DNS caching (ISP and client side)

web proxies

client side application caches

and all the hardware caching again

a short diversion:

my background is as an SA and DBA. i’ll be focusing data safety facets of caching

disk caches

disk controller caches

database caches

memcached layer

operating system caches

③which are redundant?

get moving!

④which are a risk?

disks lie

raid controllers lie (sometimes)

⑤ benchmarking

every infrastructure is different

every benchmarkhas to take that intoaccount

⑥ monitoring

measure multiple points

only you can preventfiredrills

tools to managethis insanity—

InnotopPercona toolkitsysbenchcacti templatesnagios

credits

flickr

• license plate – severud• tools – meanestindian

other

• 3ware image via http://www.xbitlabs.com/

• remaining images istockphoto

CIO Meteor EntertainmentProgram Chair OSCONProgram Chair PLMCEBoard Member Blue Gecko

Chef CommunityMySQL Community

sarah.novotny@gmail.com@sarahnovotny

stuff I do