[appengine-java] Re: Always On not working properly

There have been a few threads discussing this recently. It appears that they are bringing in the new instance scheduler in the background, which will eventually replace the "Always On" concept. Unfortunately this has the side effect that the current Always On instances aren't being used in the

[appengine-java] Re: Always On not working properly

Now it's starting to get even worse than before Always On was activated! See above picture (with a lot of red in it, lol). The app engine id is: tweetvote2 -- You received this message because you are

[appengine-java] Re: Always On not working properly

Ok, but as Always On is working now is totally unacceptable. Google needs to fix this immediately imo. -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To view this discussion on the web visit https://groups.google.com/d/msg/googl

[appengine-java] Re: Always On not working properly

Yep same here, lots of warmup requests and slow responses to users. Quite costly CPU wise too. Really annoying. Francois -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To view this discussion on the web visit https://groups.g

[appengine-java] Re: Always On not working properly

I'm not sure if it's worse with Always On activated or inactivated. I activated that option because new instances were starting all the time, like every second when it was really bad. So Always On is perhaps better than that, but it's really horrible either way! I'm surprised that Google hasn't

[appengine-java] Re: Always On not working properly

Isn't it possible to treat instances similar to pages in a virtual memory page swapping algorithm? And if too many page swaps are made too frequently then either the page swapping algorithm sucks or there is too little physical memory (or both :D). I doubt that the Google engineers are using a

[appengine-java] Re: Always On not working properly

Also, if I remember correctly, in the new pricing model there will not be possible to reserve instances other than to cut down the cost; there is no guarantee that the instances will always be loaded. So for an application with low traffic, even with operational support and several reserved fro

[appengine-java] Re: Always On not working properly

And why so complicated price model? Isn't it possible to normalize difference things like CPU, number of instances, data storage and bandwidth cost etc into a single metric? And then have enough physical servers etc so that too much instance swapping is prevented. With a normalization like that

[appengine-java] Re: Always On not working properly

switching to the high availability data store fixed this for me. On Aug 25, 10:30 am, Anders wrote: > I switched on the Always On option and it works inasmuch as the dashboard > shows three resident instances but new instances are started sometimes with > only a few seconds between page accesses

[appengine-java] Re: Always On not working properly

I use the high replication datastore if that's what you mean by high availability. -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/d

[appengine-java] Re: Always On not working properly

Another problem when switching to Always On is that sometimes when I upload new versions of the application no change happens! Even when I wait several minutes after the upload. Is Google App Engine really a finished product? Or is it still in a trial version? It's starting to feel really shaky.

[appengine-java] Re: Always On not working properly

Are you talking about static resources, or your Java compiled code? The former can be cached on the front-end servers, so you need to use some cache-busting techniques to get around that if you are updating static resources. I can't say I've ever experienced issues with Java code being stale.

[appengine-java] Re: Always On not working properly

I should add that, as far as I'm aware, GAE is still in beta - it is due to come out of beta by the end of the year I believe. -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To view this discussion on the web visit https://group

[appengine-java] Re: Always On not working properly

In this case it was the Java code. First it it took me several uploads to make the change happen. Now it's not even working with several uploads. I have used appcfg rollback recently and will try that again if I can get the upload to work. Frustrating! -- You received this message because you

[appengine-java] Re: Always On not working properly

Now the performance is pretty good. And to not appear as a total jerk I want to add that overall GAE is really awesome. Now I can focus on the really challenging part which is to generate massive traffic. And then it will be interesting to see how GAE will manage that. :-) -- You received this

[appengine-java] Re: Always On not working properly

Hi Anders, Part of the new billing plan is to have Always on go away, they are going to be replace by Min Idle Instances. as of SDK 1.5.2 we made some changes to the Scheduler on how the reserved instances behave. I would recommend you should take a look at this two threads on the groups where

[appengine-java] Re: Always On not working properly

Hi Jose, Ok, setting idle instances would be similar to Always On I assume. Plus I read in one of those threads that they are working on fixing some instance scheduler bug. So that should make the performance smoother. Unless they try to squeeze too many instances into too few physical servers.