What would you need all those threads for in a web App? If you were crunching DNA, or calculating the path of particles from the big bang that would make sense...
But if your App completes a request in less than 3 seconds, you would still be able to server 10 users a second, 600 users a minute, 864k requests a day. If having 3 threads sped this up to 1 second, the math would work out to the same number of request potentials. Do to the CPU time limits on a task, it is unlikely you would want 2000 threads because you'd burn through your Cycle limit just setting up those threads. I'm assuming from the Smiley after your comment about Cranking up the max threads, that you THINK you are doing something clever. In all likely unless you are doing some super computing apps on a CPU(s) with enough cores to support that number of threads you are just wasting cycles in thread management, and time slicing. -Brandon Wirtz -----Original Message----- From: google-appengine@googlegroups.com [mailto:google-appeng...@googlegroups.com] On Behalf Of Adligo Sent: Tuesday, September 01, 2009 5:34 PM To: Google App Engine Subject: [google-appengine] 30 Max simultaneous requests (maxThreads)? Hi, I am developing a app (or more than one) that I would like to host on Google App Engine, however the architecture of the app involves cranking up the maxThreads (I am using my home grown hosting which now has Tomcat set to 2,000 maxThreads :) ). For example (1 six+ year old machine in my basement) http://zeuhl.adligo.com/gwt_util_demo_v3_1/GwtDemo.html?show_log=true --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
