It is not a hard limit. I suspect they will let you pay for more once it is out of experimental status.
I've found the log service to be a little slow when fetching a lot of records in a row. In my tests it can take 15 minutes of looping (max batch size) to fetch 1000000 records. So if you're using this on an app with a lot of requests you probably want to scan "often." (ie don't pull once a day on an app with 20000000 requests per day.) Robert On Thu, Feb 16, 2012 at 04:29, Andrin von Rechenberg <[email protected]> wrote: > @Google: Is this a hard limit that will stay around? Can it be increased? > > I'm planning to implement prodeagle using the logservice instead of > memcache. > But 1000000 reads per day is just too low if you have more than 1000000 > queries > per day. Are there any other alternatives? > > Cheers, > -Andrin > > > On Tue, Jan 24, 2012 at 8:34 PM, Robert Kluin <[email protected]> > wrote: >> >> You may want to mention why it "all comes to nothing." >> >> >> >> Robert >> >> >> >> >> On Tue, Jan 24, 2012 at 09:25, [email protected] <[email protected]> wrote: >> > I've spent two days working on a feature based on the LogService, it >> > seems it >> > all comes to nothing :\ >> > >> > You could at least leave a small note on the documentation related to >> > it. >> > here for example: >> > http://code.google.com/appengine/docs/python/logservice/ >> > >> > Do you plan to make it billable? >> > >> > Daniel C. <http://theosp.me/> >> > >> > On Jan 19, 12:08 pm, Alexis <[email protected]> wrote: >> >> Hi >> >> >> >> We noticed a few days ago that starting from the middle-end of the >> >> day, a new quota line now appears in one of our app dashboard: >> >> "Log Records Received - 95% - 946,267 of 1,000,000" >> >> >> >> This line is not there in other apps or at the beginning of the day. >> >> So it must appear only because we are going to reach the quota limit. >> >> That's fine, but this quota does not appear in the "Quota details" >> >> section of the dashboard, and is not mentioned in the quotas >> >> documentation neither in the LogService documentation. In other words >> >> I have no clue of what is it and could not anticipate it. >> >> >> >> We only have an average 15 requests/sec so it's more than 1 million >> >> requests a day, the quota can't be that we can't log more that 1M >> >> requests right? >> >> >> >> I think it may be linked to the new LogService API that we are >> >> starting to use. Is it because we read too many records using this >> >> API? >> >> >> >> Can someone shed some light on this? Did I miss something? >> >> Thanks >> > >> > -- >> > 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. >> > > -- > 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.
