Featured post
memcached - Memcache(d) vs. Varnish for speeding up 3 tier web architecture -
i'm trying speed benchmark (3 tier web architecture), , have general questions related memcache(d) , varnish.
what difference?
seems me varnish behind web server, caching web pages , doesn't require change in code, configuration.
on other side, memcached general purpose caching system , used cache result database , require change inget
method (first cache lookup).can use both? varnish in front web server , memcached database caching?
what better option?
(scenario 1 - write,
scenario 2 - read,
scenario 3 - read , write similar)
- varnish in front of webserver; works reverse http proxy caches.
- you can use both.
- mostly write -- varnish need have affected pages purged. result in overhead , little benefit modified pages.
- mostly read -- varnish cover of it.
- similar read & write -- varnish serve lot of pages you, memcache provide info pages have mixture of known , new data allowing generate pages faster.
an example apply stackoverflow.com: adding comment invalidated page cache, page have cleared varnish (and profile page, isn't worth caching begin with. remembering invalidate affected pages may bit of issue). comments, however, still in memcache, database has write comment. nothing else needs done database generate page. comments pulled memcache, , page recached until affects again (perhaps voting answer up). again, database writes vote, other data pulled memcache, , life fast.
memcache saves db doing lot of read work, varnish saves dynamic web server cpu load making generate pages less (and lightens db load bit if not memcache).
- Get link
- X
- Other Apps
Comments
Post a Comment