Hi all,
I've used Google App Engine for more than 2.5 years. I suffered a hard time
to read the English documents, articles and the SDK source code. I thought I
knew it very well, but now I find I was wrong.
It was a great platform to build either small or big web services, but I
believe it won't
Sad to hear this Keakon.
I too had to pick up Python for GAE, over 3 years ago and now just love
working on Python and GAE. The current pricing changes to take effect
without multi-threading support for Python, screws those early adopters
too.
May be we should meet at the *App-Engine-olics Anonym
Sad to hear this.
On Fri, Sep 2, 2011 at 3:08 PM, keakon lolicon wrote:
> Without memcache, the free quota will be used up in less than 500 PVs (I
> also need fetch articles, comments, etc.). Though I have used memcache very
> aggressively, I have no way to handle 10k PVs within the free quota si
Our version of Memcache is a bit different. There are two LRUs for Memcache:
an app specific LRU and a global LRU for that Memcache instance. Users of
Memcache find that if some value has not been accessed in ~a few hours, they
are typically evicted due to the global LRU.
While this might be unfri
+1 to Ikai's comment. We wrote a little API which checks memcache, then
datastore, and it works quite well.
adam
--
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/go
Hey Keakon,
Hope you don't leave the App Engine community completely. You seem
to be a good developer, and you've been a good member of the community
by helping others and participating in discussions.
Robert
On Fri, Sep 2, 2011 at 02:08, keakon lolicon wrote:
> Hi all,
> I've used Go
