Doesn't that then beg the question of how many requests one 'Always On' instance could handle and what's the typical performance of an instance in terms of CPU, network requests, etc?
With 8 instances I would guess there's some distributed caching overhead that may be unwanted or undesirable if the app doesn't have lots of traffic. -brian On Jan 17, 8:42 pm, Robert Kluin <[email protected]> wrote: > Out of curiosity, why? Generally speaking, the more instances your > app has the more likely it is that a new request will be serviced > quickly. You are not charged for the additional instances, unless > they are doing something (in which case you probably needed them > anyway). > > Robert > > On Mon, Jan 17, 2011 at 22:35, brianl <[email protected]> wrote: > > Just checked my Instances allocations... Seeing the 3 'Always On' > > instances and 5 Dynamic instances. The 5 Dynamic instances seems > > unusually high. So guess I have 8 instances total. There's very > > little traffic to the app to cause so many instances to be running. > > I'd like to be just running the 3 'Always On' instances and no Dynamic > > instances, is this possible? If so where's the setting to have NO > > Dynamic instances running when 'Always On' is enabled? > > > On Jan 17, 1:41 pm, "Brandon Wirtz" <[email protected]> wrote: > >> Always on helps if you only need 3 instances to keep things running. If > >> your app requires 4 instances be running all the time you won't see any > >> benefit. If on the other hand you serve one request an hour, you'd see a > >> lot of benefit on that one request. > > >> Without knowing what you are doing, or why you are doing it we can't help > >> you diagnose if what you are doing is sane and rational, or if it is > >> something in your design that is causing the issue. > > >> From: [email protected] > >> [mailto:[email protected]] On Behalf Of brianl > >> Sent: Monday, January 17, 2011 11:53 AM > >> To: [email protected] > >> Subject: [google-appengine] Always On - Amount of Loading Requests the same > > >> According to the docs the 'Always On' feature mitigates the impact of > >> loading requests. I've been running w/ the 'Always On' feature for several > >> days. I thought I'd see far fewer loading requests, but it appears to be > >> the same as before. There are still cases where I'll see loading requests > >> just a few minutes apart. Most times I see loading requests occur about > >> 50~60 minutes apart. So far I'm not seeing the benefit of the 'Always On' > >> feature. It appears to be a waste of money. > > >> -- > >> You received this message because you are subscribed to the Google Groups > >> "Google App Engine" group. > >> 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 > >> athttp://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 [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > For more options, visit this group > > athttp://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 [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.
