Why are you doing this rather than using a service such as beaconpush.com?
As for wanting limits thoroughly documented, I could not agree more.
This is some thing that should be done, and I frankly can't understand
why it isn't. I would like to see something like:
http://code.google.com/p/googleappengine/issues/detail?id=5677
Along the same lines, it is very annoying to hit temporary
(undocumented!) quotas, such as datastore operations per minute, then
have no record of exactly what quota was hit. I'd love to see a daily
log of *exactly* every quota an app hits with enough detail for me to
tell Google what I'm hitting:
http://code.google.com/p/googleappengine/issues/detail?id=6296
Robert
On Tue, Feb 21, 2012 at 14:58, Markus <mca...@gmail.com> wrote:
> Ouch! Really??? This is a MAJOR deal-breaker for one of my projects.
>
> But if that's the case, what good is <max-concurrent-requests>? Is it
> really only there to limit the number of requests even further?
> Wouldn't it be brilliantly sensible and useful to use this setting to
> specify the size of the thread pool?
>
> Do you know if this is a soft-limit? I.e. could I request an increase?
> With the app I'm working on, I'd love to have many 10s of thousands of
> requests simultaneously locked in a wait() on a single backend. This
> should consume virtually no CPU and probably not much memory either.
> But with 10 threads (i.e. 10 requests) per instance, there is no way
> this would work.
>
> In case you guessed it: I am indeed trying to build my own much
> improved version of the Channels API.
>
> Thank you for the data-point. This might also explain the 6-request-
> limit for my backend, if there are 4 other things going on in parallel
> that I didn't initiate.
>
> Markus
>
>
>
> On Feb 21, 8:46 pm, Jeff Schnitzer <j...@infohazard.org> wrote:
>> I suspect one of the missing pieces of information is that multithreaded
>> Java instances can only handle 10 threads right now (or so I have been
>> told).
>>
>> Jeff
>>
>>
>>
>>
>>
>>
>>
>> On Tue, Feb 21, 2012 at 2:05 PM, Markus <mca...@gmail.com> wrote:
>> > Hi,
>>
>> > first of all, let me say that I think AppEngine is one of the greatest
>> > ideas ever. I love the concepts behind it; even some of the
>> > restrictions it comes with that allow it to be so scalable.
>>
>> > Unfortunately, though, I keep running into random undocumented limits,
>> > that force me to rewrite my code frequently, or to even abandon GAE
>> > for certain projects altogether.
>>
>> > Right now, I am fighting with concurrent requests and have found
>> > several limits that I didn't see documented anywhere and I am not sure
>> > whether I should be seeing them, or whether I am doing something
>> > wrong. So I am hoping one of the Google engineers is available and can
>> > give some background info regarding some of the limits/quotas/strange
>> > behaviors I found with one of my test apps:
>>
>> > - Frontend instances can handle only about 30 requests/s (qps). (I've
>> > seen that number mentioned in posts somewhere, but I can't find it in
>> > the docs.)
>>
>> > - Frontend instances keep getting created by the scheduler "randomly",
>> > sometimes already when I only have 2-3 requests pending, even if I set
>> > the respective Application settings to max 1 idle instance and max 15s
>> > request latency.
>>
>> > - Backend instances can handle only 10 requests/s (qps), independent
>> > of instance class. (I haven't seen this mentioned anywhere.)
>>
>> > - Backend instances can only have 6 requests open simultaneously,
>> > independent of how I set max-concurrent-requests. (Someone mentioned
>> > this in a post in 2009 for a frontend instance, but I can't find any
>> > infos on backends.)
>>
>> > - My backend sends "503 Service unavailable" errors randomly, if there
>> > are too many requests pending. Unfortunately I can't get a number on
>> > when this happens (how many requests is too many). Also, I found this
>> > surprising since I thought that the whole point of backends was to not
>> > have these sorts of limits.
>>
>> > Any light anyone can shed on these questions would be much
>> > appreciated.
>>
>> > I am most interested in the <max-concurrent-requests> setting in
>> > backends.xml. Should this do something? I guess if I had written GAE
>> > (I wish), this would specify the size of the thread-pool for request
>> > servlets? Is there a limit/quota for how high I can set this number?
>>
>> > Are there any differences in these limits between paid and free apps?
>> > How about Python vs. Java?
>>
>> > Do the 9 hours per day of free backend use also apply for paid apps?
>> > (Or more general: are all free quotas still free for paid apps?)
>>
>> > And, I guess, the question that non-Google-engineers can answer to
>> > help me in this quest is:
>>
>> > - Has anyone been able to exceed any of the above mentioned limits? If
>> > so, do you know how?
>>
>> > Thank you very much for your help,
>>
>> > Markus
>>
>> > PS: Is there a chance we can get all quotas/pricing information on a
>> > single page? Currently there are:
>> > -http://code.google.com/appengine/docs/quotas.html
>> > -http://code.google.com/appengine/docs/billing.html
>> > -http://www.google.com/enterprise/cloud/appengine/pricing.html
>> > -http://code.google.com/appengine/docs/java/backends/overview.html
>> > (at the bottom)
>> > - the Dashboard of the app itself
>> > - and potentially many others that I haven't found yet
>>
>> > --
>> > You received this message because you are subscribed to the Google Groups
>> > "Google App Engine" group.
>> > To post to this group, send email to google-appengine@googlegroups.com.
>> > To unsubscribe from this group, send email to
>> > google-appengine+unsubscr...@googlegroups.com.
>> > 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 google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> 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 google-appengine@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en.
