Hi Lucas, The write-rate applies to a single entity group, not the overall datastore. The number of writes you'll be able to sustain per second will depend on a lot of factors. You may not need to use the task-queue at all, what about trying to put in the user-request and only deferring to the task-queue on error?
The hard part about something like a logging-system is that you'll probably want to index on something like event time, which is could put a lot of strain on your indexes. See Ikai's awesome illustrations: http://ikaisays.com/2011/01/25/app-engine-datastore-tip-monotonically-increasing-values-are-bad/ I've been able to sustain write-rates of around 7,500 entities per second on entities with a few single property indexes, putting them in batch of around 17 entities per put. I'm sure you could get higher write rates with some applications. Obviously it would be easier to get far lower rates with a complex app, or with a bad design, as well. Robert On Tue, Mar 15, 2011 at 10:29, Lucas <[email protected]> wrote: > do you recommend, whether to use task queue, if i need very high write > (new record each time, no update) . like log system ? how may write > per second, datastore able to support? > > -- > 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. > > -- 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.
