Hi all, Although I'm not sure if the two are connected, after updating to the 1.7 SDK, blobstore writes using the Files API have become very slow on finalization, frequently failing completely with an IOException when the blobs get to around 2 megabytes. These requests fail after running for 30 seconds. I've filed a production issue here: http://code.google.com/p/googleappengine/issues/detail?id=7992
I wonder if anyone else has seen such a slowdown. Also - this leads me to a question about the File API in general. I know Google doesn't comment on feature timing issues, but just in case anyone has any insight... is it a bad idea to rely on the File API? Its been experimental for such a long time that I'm worried that it will eventually be eliminated, just because it hasn't been promoted already. Its also the weakest link in my app - it produces a lot of random errors, more than any other piece of GAE. If relying on the Files API is a bad idea, how would you guys accomplish the following: I'm using GAE as a sync-backend for a mobile app. The mobile app receives deltas from the GAE app, and these deltas are pre-generated. Generating them on demand could possibly take too long, thus the offline pre-generation. The deltas could be larger than the datastore entity-size limit, which is why I'm storing them as blobs - and then serving them to the app when they're needed. So, if not for the Files API, how would you guys store these deltas? I really hope to avoid the complication of using an additional system that's external to GAE, especially when the blobstore+Files API seem so perfectly suited to the task. Thanks, Mike -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. 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.
