When it comes to writes I call it the "times two phenomenon". I have NO IDEA why you can't do anything that is not 2 writes???
e.g. If you have a very simple Entity with 5 properties (none set to the NON default status of Unindexed) and you save it, it is 12 writes. Key <http://localhost:8080/_ah/admin/datastore?&kind=Test&order=__key__>Write OpsID/Name<http://localhost:8080/_ah/admin/datastore?&kind=Test&order=__key__> firstName<http://localhost:8080/_ah/admin/datastore?&kind=Test&order=firstName> four <http://localhost:8080/_ah/admin/datastore?&kind=Test&order=four> lastName<http://localhost:8080/_ah/admin/datastore?&kind=Test&order=lastName> six <http://localhost:8080/_ah/admin/datastore?&kind=Test&order=six>three<http://localhost:8080/_ah/admin/datastore?&kind=Test&order=three> agtwaXhvdG8tbGl2ZXILCxIEVGVzdBiNAQw12141JoedoorBobsticksfree So you get slammed with 12 writes. Each property is 2 writes. Here is a PropertyLess Entity Key<http://localhost:8080/_ah/admin/datastore?&kind=PropertyLess&order=-__key__>Write OpsID/Name<http://localhost:8080/_ah/admin/datastore?&kind=PropertyLess&order=-__key__> agtwaXhvdG8tbGl2ZXITCxIMUHJvcGVydHlMZXNzGI4BDA2142 2 writes. Who needs properties anyhow? That would mean you could query on them. Queries return results, results are reads. Reads cost money. Oh wait, that is what memcache is for... wait a sec, memcache took down my whole site Monday from MemcacheServiceExceptions http://code.google.com/status/appengine/detail/memcache/2011/12/12#ae-trust-detail-memcache-get-latency "Also in my app app engine often spins up idle instances (that I cannot get rid of no matter what I configure) and send them exactly 1 request every 15 minutes so that I'm being charged the whole time for this instance I don't want." This happens to me also... Why is it if you have 6 instances, 2 of them get most of the requests 3 of them get none and occasionally App Engine will start up a 7th instance while the idle 3 still get nothing? Don't get me wrong. I LOVE what App Engine stands for and I have all the respect in the world for the App Engine team. BUT, I have been through SO much grief ranging from random app engine problems to having to migrate to an HR datastore to dramatic increases in pricing. When I signed up for this (old pricing), I thought the pricing would eventually get better (almost like gmail and disk space), but instead it went the opposite. Had my experience been perfect here and my app had run flawlessly all this time, I would have had no gripes and shut up and spent the extra cash without blinking. But, instead I have experienced hair loosing problems, massive variations in performance and got stuck with a much larger bill. -- 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/-/DElz4NPSc8oJ. To post to this group, send email to [email protected]. 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.
