Issue 17 in geodatastore: Caching KML or writing to disk

[codesite...@google.com]

Issue 17: Caching KML or writing to disk
http://code.google.com/p/geodatastore/issues/detail?id=17

New issue report by Layne.Moessing:
I have found that geodatastore's with more than about 50 points causes App
Engine to give High CPU warnings when requesting the complete KML via the
request.

http://geodatastore.appspot.com/gen/request?operation=get&output=kml

I would assume most maps are viewed more than added to.

Is there a way for geodatastore's App Engine to cache the KML file, and
update the cache every time a new element is added to the database. This
might alleviate the CPU warnings.

I don't think app engine allows writing to a file, but if it does appending
to the file could also be a solution.

Issue attributes:
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

[codesite...@google.com]

Issue 17: Caching KML or writing to disk
http://code.google.com/p/geodatastore/issues/detail?id=17

Comment #1 by BarryBHunter:
Yes this would be easyily possible using memcache.

(I believe the georss output actually produces more cpu warnings - probably
as that
uses templates, - but that again should be easily cacheable using memcache)

Issue attribute updates:
Labels: -Type-Defect Type-Enhancement

[codesite...@google.com]

Issue 17: Caching KML or writing to disk
http://code.google.com/p/geodatastore/issues/detail?id=17

Comment #2 by pamela.fox:
Great-- I wanted an excuse to try out memcache. I'll experiment with this
soon.