This looks like you could use a template to construct the memcache content. If gathering the time for the template data is very easy, using a memchached version would slow you down. If you use Django templates, they are cached in the server instance. No need to read them again from file. You can even use the Django template cache to cache static files (no field substitutions) in the server instance.
You can make a template loader that reads gzip files. 2010/11/3 pdknsk <pdk...@googlemail.com>: > Sorry, I didn't mention that I also do a simple string replace where I > insert time() and also two or three other string replacements based on > user agent, so purely static files don't work. > > You're right, the performance difference is negligible, and reading > from file might even be faster if I didn't use gzip to open them. I'll > try with uncompressed files in the next update. I mostly used memcache > because reading from memory should be more efficient and put less > strain on the system than reading from disk. Is open() quota free? It > seems to be. -- 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-appeng...@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
