MemCache Vs. EdgeCache
Brandon Wirtz
While I’m not saying you should ditch memcache for speeding up your output. If you are looking at the effort to implement Memcache through out your code, or getting your headers right to enable edgecache, consider this.
In all 3 of the following apps EdgeCache “Hits” were at 40-65%
MemCache:
'hits': 2,425, (4%)
'misses': 55,618,
'items': 2,696,
'bytes': 34,992,253,
'hits': 44,668, (27%)'misses': 163,823, 'items': 1,170, 'bytes': 1,515,333, JeffProbst.com (High Volume, only like 25 pages of content, I think Edge misses are due to geographic diversity)'hits': 50,943, (74%)'misses': 68,942, 'items': 100, 'bytes': 618,267,
The larger your data set the lower your memcache success will be. From what I can tell Memcache never goes over 3000 items or 35 Megs I haven’t been Logging it constantly, so I’m not sure if it is an item or a Meg limit.
If you are writing a VERY small app. Using only 1 always on instance writing for Instance memory ensures a much larger cache hit ratio because you get more space and unless your instance resets the data seems to persist.
Brandon Wirtz
I should have also mentioned that the combined cache hit of all tiers of our system is 93%.
50% Edgecache
12% Local Instance Memory
8% MemCache
23% DataStore
With edge Cache off
The numbers look pretty close to the same
14% Local Instance Memory
10% MemCache
69% DataStore
Turning off Local instance memory has a NEGATIVE effect on Memcache because of data turn over being high because of the limited size of the Memcache.
--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To post to this group, send email to google-a...@googlegroups.com.
To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Tim Hoffman
Brandon Wirtz
Edge Cache is Infinite :-) So if you know how long a page is good for, and you can do things via Get Requests it is the way to go.
I’m guessing Jeff Probst’s site could get to 70% cache hits or better easily. 100-ish objects I could probably load the whole site in to ram and not have a tiered system, and could serve everything from 1 or 2 instances, but that’d be code for a single site with atypical usage and not enough billing to support it.
--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/r6ytOqg9yPoJ.
Tim Hoffman
Brandon Wirtz
Picky Picky. If you can’t get your users to request the same page more than once, maybe you should make your pages worth coming back for. :-)
From: google-a...@googlegroups.com [mailto:google-a...@googlegroups.com] On Behalf Of Tim Hoffman
Sent: Sunday, November 27, 2011 5:30 AM
To: google-a...@googlegroups.com
Subject: Re: [google-appengine] MemCache Vs. EdgeCache
Infinite and completely useless for some types of apps ;-)
T
--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/jlGF0wQmxJcJ.