Will there be a way to separate start up activity from request activity, so that initial requests will not be killed prematurely with a deadline exceeded error?
On Nov 30, 2009 5:15 PM, "Toby Reyelts" <to...@google.com> wrote: Hi Jeff, First, it's definitely a net win for us to spin down an application if it doesn't receive much traffic, even if the loading requests are significantly more expensive. This is one of the main reasons why we're able to offer everyone free quota on App Engine - it doesn't cost us extra money to host your app when it's not actually receiving traffic. Second, as far as your free quota goes, it should be very difficult (impossible?) to use it up with just loading requests. The number of loading requests you get is inversely proportional to the traffic your app receives. The more CPU you chew up due to incoming traffic, the less CPU you chew up due to loading requests. Third, as Ikai says, we're continuously and aggressively working on optimizations for reducing both the latency of and the amount of CPU spent on loading requests. Keep a lookout for announcements in upcoming releases. Finally, I've filed a feature request<http://code.google.com/p/googleappengine/issues/detail?id=2456>in the issue tracker for reserving JVMs. If you'd like to be able to pay to reserve a JVM, please star the issue. Feel free to leave a comment about what you feel would be a reasonable pricing scheme. On Mon, Nov 30, 2009 at 3:50 PM, Jeffrey Goetsch <jeffg....@gmail.com> wrote: > > The billing opti... -- You received this message because you are subscribed to the Google Groups "Google App Engine for... -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
