In my current understanding, to run a job on a backend, a http request must be sent from a general front instance to the backend, right?
On Sep 28, 5:56 am, Rishi Arora <rishi.ar...@ship-rack.com> wrote: > Consider using a backend for cron jobs. I use my once every hour, and each > usage lasts about 3 minutes. This gives me a total backend instance hour > usage of 18 minutes every hour (15 minutes mandatory idle time charge) = > 18*24 = 7.2 hours, which is under the 9 instance hour free backend quota. > > > > > > > > On Tue, Sep 27, 2011 at 4:29 PM, Tapir <tapir....@gmail.com> wrote: > > Thanks for clarification. > > > I think one idle instance is not enough. > > I often (about 15% possibility) load my app page very slowly. > > I think the possible reason is when a visit coming at the same time > > the cron jobs > > is running, a new instance must be started for the visit request. > > As the cron jobs need some seconds to finish. > > > So I think it will make a better user experience if gea can provide an > > option to let > > the crons jobs always run in a new separated instance. The new > > separated instance > > will not handle normal visit requests. > > > On Sep 28, 4:49 am, "Gregory D'alesandre" <gr...@google.com> wrote: > > > Agreed. If you actually need 3 idle instances than it will indeed cost > > you > > > that much but for many applications 3 idle instances is overkill, > > especially > > > with concurrent requests enabled for java. Many java apps will be fine > > with > > > a single idle instance. Since you get 28 instance hours/day for free, > > this > > > means you can keep 1 idle instance running all the time without an > > > additional fee. Also, the $9 is a minimum spend not a fee (this was > > changed > > > from the original model) so it would just be $105.60. > > > > Greg > > > > On Tue, Sep 27, 2011 at 1:11 PM, JH <ja...@mhztech.com> wrote: > > > > yes, under new pricing a min idle instance of 3 will be very > > > > expensive. > > > > > On Sep 27, 2:28 pm, Tapir <tapir....@gmail.com> wrote: > > > > > On Sep 28, 3:22 am, Tapir <tapir....@gmail.com> wrote: > > > > > > > For a java app, to avoid slow warm-up problem, 3 instances are > > needed > > > > > > to run always. > > > > > > The $9/month "always on" feature is perfect for avoiding this > > problem. > > > > > > > In my current understanding, under the new price model, > > > > > > the "always on" feature will cost $0.08 * ( 24 + 24 - 4) * 30 = > > > > > > a spell erro, no "* 30" here > > > > > > > $3.52/day, > > > > > > this means for small java apps, if you want to make a good user > > > > > > experience > > > > > > for your java app, you will pay at least ($105.6 + $9) / per month, > > > > > > right? > > > > > -- > > > > 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.
