I've been digging into where may app is spending its mcycles.  By
using memcache I've gotten all of my requests that only read data down
well under the 1000 mcycle overall average request processing limit;
however, I'm seeing that it takes about 1000 mcycles to update a
single entity (not indexed, not very large either).

Is this in line with what other folks are seeing?
--~--~---------~--~----~------------~-------~--~----~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to