On Mon, Mar 21, 2011 at 1:56 PM, Matija <matija.jerko...@gmail.com> wrote: > Can you explain 'concurrent requests for Java' ?
(warning: I don't work for the big G) Believe it or not, all GAE/Java requests are all single-threaded right now... similar to the GAE/Python architecture. It doesn't matter much for your app since GAE spins up as many instances as necessary to handle load, but it's inefficient - especially considering the ~75MB memory footprint of each JVM compares unfavorably to ~13 for a Python VM. Looks like that restriction is about to be removed. Google: Why not just make this the default? Or at least announce that it will become the future default, so people don't start counting on single-threaded behavior. Presumably we've all been coding to the servlet API, which is very specific about thread behavior. I don't think anyone realized that requests were single-threaded, and if they coded with this (undocumented and spec-violating) assumption, they deserve to have their apps break. I imagine that you could cut down the total # of instances running in the cluster by a significant factor (2x, 3x, more?) this way. My hope is that this efficiency will ultimately lead to a cheaper and faster appengine... but people need some incentive not to use "single thread mode". Jeff -- 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.
