Well, I've submitted 2 or 3 tickets to their support team last week
and haven't heard back yet. Perhaps I'm doing something wrong.
As far as how our app did on the app-engine: it was pretty smooth. I
think the main issue we ran into was the 10 writes per entity group
per second. I think that restriction may force us onto a different
platform. I think we could have worked around that restriction by
employing more clever memcache usage, especially now that there is CAS
enabled on the memcache, but I'd be slightly nervous about updates
living in memcache and getting dropped before we wrote them to the
datastore. My clients pretty much decided they want to try another
hosting solution, so I guess that's my only option lol.
Thanks for the reply!
On Sat, Feb 12, 2011 at 5:34 AM, systemsplanet m...@systemsplanet.com wrote:
the app engine team recently fixed a problem
I was having in about 12 hrs. I couldn't add
a new application, GAE forgot I had already
authenticated my mobile phone number.
as for your ap, I'll be interested to see
if an ap with expected high contention
will work well on gae. seems like gea is
optimized for high-reads and few
non-contending writes (like a blog).
.
On Feb 11, 1:37 am, bcottam bcot...@gmail.com wrote:
Good point Robert, I'm not sure if it's just the datastore. My users wind
up getting a 500 error on requests that just read data, usually even if the
datastore has issues, you can still read from it.
I'd be comfortable using memcache, but I'd want to ensure it had the same
data integrity as the datastore (or something close anyhow). The nice thing
about the datastore is that there is optimistic locking, so I know when
there's contention. Currently, our users collectively modify data at about
the same time (like 7-12 updates in a single second from several users),
it's pretty important that I keep them in order, so I currently have my
writes wrapped in a datastore transaction with a loop that runs about 5
times or until the transaction succeeds. Has anyone managed that type of
contention in the memcache? If so, I'd love to hear some techniques that
can ensure no update tramples a previous concurrent update.
I've submitted inquiries to the billing and CPU request form, but haven't
heard back. Does it usually take longer than 24 hours to hear back from the
app-engine support team?
Thanks
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To post to this group, send email to google-appengine-java@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en.
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To post to this group, send email to google-appengine-java@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en.
