This really should be documented (if it is already and I missed it, apologies).
Given a hard limit of 10 threads per instance, does it make sense to use anything other than an F1 instance, if you have primarily RPC-blocked requests (which I assume many, if not most, App Engine apps are)? On Friday, June 15, 2012 11:34:47 AM UTC-4, Jon McAlister wrote: > > > > > >> } Is there still a hard limit of 10 threads? > >> > >> Yes, but probably not for the reason you expect. The primary > >> issue we run into is memory management. If we raised the default > >> to 100, many apps would then see out-of-memory deaths (more than > >> they do now), and these deaths show up differently for > >> python/java/go. The right path forward is more intelligent > >> algorithms wrt memory, providing configurability, and so on. This > >> is an example of the kinds of projects we work on for the > >> scheduler, but as with any team we have to prioritize our > >> projects. I'd recommend filing this (or any other desired > >> scheduler enhancements) on the public issue tracker so they can > >> get feedback/data/votes. > > > > Does this limit still apply to larger instances? If an F2 has twice > > the memory and CPU of an F1, it should be able to handle the same load > > as two F1s. In theory, any app which requires dozens of instances > > would be better off switching to F4 frontends. But not if there's > > still a 10 thread limit. > > It does not presently consider this. It seems like a reasonable approach. > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/J8375CmJH6cJ. 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.
