[google-appengine] Re: Using memcache might be free, but it's costing you money with instance pricing! Use instance caches if possible.

Remember to implement a mutex system in the in-process caching mechanism or your instance will fail randomly when the new py2.7 version will be rolled out. -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web

[google-appengine] Re: Using memcache might be free, but it's costing you money with instance pricing! Use instance caches if possible.

in new pricing model exist something like memcache data transfer price? -- 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-appengine@googlegroups.com. To unsubscribe from this group, send email to

[google-appengine] Re: Using memcache might be free, but it's costing you money with instance pricing! Use instance caches if possible.

Hi Santiago, On Sep 8, 9:01 pm, Santiago Lema jacques.l...@gmail.com wrote: Since this app basically serves semi-static content (it's updated once a day) I used AppEngine's memcache to serve every request. [...] So I just added another level of caching before memcache: a simple python dict

[google-appengine] Re: Using memcache might be free, but it's costing you money with instance pricing! Use instance caches if possible.

Thanks a lot! I'll definitely try this. On 9 sep, 03:40, Tammo Freese i...@flockofbirds.net wrote: HiSantiago, On Sep 8, 9:01 pm,SantiagoLemajacques.l...@gmail.com wrote: Since this app basically serves semi-static content (it's updated once a day) I used AppEngine's memcache to serve

[google-appengine] Re: Using memcache might be free, but it's costing you money with instance pricing! Use instance caches if possible.

Tammo, I thought you might like to know I quoted you in my fresh blog post on this matter: http://www.smallte.ch/blog-read_fr_34003.html -- 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-appengine] Re: Using memcache might be free, but it's costing you money with instance pricing! Use instance caches if possible.

Ok, I have just tested it and it seems to work beautifully (at least for all the requests that didn't include a random value!). -- 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-appengine] Re: Using memcache might be free, but it's costing you money with instance pricing! Use instance caches if possible.

Good suggestion. At least until we have workable multithreadding I have become very reluctant to use RPCs unless absolutely necessary. It helps keep the instance number down. -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this

Re: [google-appengine] Re: Using memcache might be free, but it's costing you money with instance pricing! Use instance caches if possible.

Actually I thought using RPCs is a good way to achieve parallelism in python, before python 2.7 comes along. My app does a lot of URL fetches from external websites. This is very inefficient in terms of GAE instance uptime. If the external website takes 30 seconds to respond, my instance stays

Re: [google-appengine] Re: Using memcache might be free, but it's costing you money with instance pricing! Use instance caches if possible.

Rishi: This sounds like an excellent idea. Even with concurrent requests in python 2.7, using the asynchronous apis like this will make you application perform much better. On 9 September 2011 06:18, Rishi Arora rishi.ar...@ship-rack.com wrote: Actually I thought using RPCs is a good way to

[google-appengine] Re: Using memcache might be free, but it's costing you money with instance pricing! Use instance caches if possible.

Won't you have problems with instances that live around the time you update content? When you send the update request, that instance will update it's dict (and memcache and the datastore). If you have another instance alive at that time, it won't know about the update and will continue serving

[google-appengine] Re: Using memcache might be free, but it's costing you money with instance pricing! Use instance caches if possible.

Would be nice to have a Memcache.OnEntryUpdatedCallback... -- 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/-/wvF_Q3Q8p8MJ. To post to this group, send