[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 frontend instances, there will still be a lot of instance swapping and sluggish page loads, because in the new pricing model a reserved frontend only means a cheaper price, not that the reserved instances will be kept warm (loaded in physical memory and running). If Google keeps having too few physical servers for the number of applications (as I estimated in a previous post), then there will always be a lot of instance swapping even with the best of instance swapping algorithms, leading to poor performance and an amateurish/low-end cloud computing platform. -- 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/-/ro2HG8VBLzYJ. To post to this group, send email to google-appengine-java@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.
[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 it would be as simple as paying for electricity. The amount of resources an application needs, regardless of whether it's more CPU or data storage or bandwidth or primary memory or whatever, since the resources are normalized they can all be combined into a single parameter, would be like paying for the amount of electricity used. Too much optimization by having all kinds of parameters for customers to choose between and alter will likely be a suboptimization overall. Some customers may need to fine-tune things on a detailed level, so manual options could be available but also an automatic default price model that would be as simple as paying for electricity. I don't want to regulate the budget manually except for setting a monthly amount. And instead have an algorithm automatically distributing the budget amount for the different kinds of resources. And have statistics presented showing how much the application consumes for each resource type such as CPU, data storage etc, so that I can optimize the application without having to manually adjust the budget distribution. -- 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/-/Sp8E-UQ8QyQJ. To post to this group, send email to google-appengine-java@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.
[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 blabl...@gmail.com 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 with very low overall traffic. In the log the message This request caused a new process to be started for your application, and thus caused your application code to be loaded for the first time. pops every 10 log lines or so. Surely, with Always On activated, new instances should not be started several times every minute?! The reason I switched it on was to prevent exactly that from happening. -- 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-java@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.
[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/-/dLmzCylzGN4J. To post to this group, send email to google-appengine-java@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.
[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. -- 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/-/eTV3xUELa64J. To post to this group, send email to google-appengine-java@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.
[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. -- 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/-/b3vgcPEgGusJ. To post to this group, send email to google-appengine-java@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.
[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://groups.google.com/d/msg/google-appengine-java/-/Z05z8Gn2pXoJ. To post to this group, send email to google-appengine-java@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.
[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 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/-/IaoFHGA7jnYJ. To post to this group, send email to google-appengine-java@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.
[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 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/-/r6ZbFNcv-fsJ. To post to this group, send email to google-appengine-java@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.
[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 we discuss this in great detail: https://groups.google.com/forum/#!topic/google-appengine/nRtzGtG9790 https://groups.google.com/forum/#!searchin/google-appengine/always$20on/google-appengine/uvQ5puBz9to/qBZZgBWtoHgJ FYI, App Engine is not a trial product, we would leave preview by the end of the year. Hope this helps! Best, Jose Montes de Oca -- 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/-/iICZ-VFa8QkJ. To post to this group, send email to google-appengine-java@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.
[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. Because then even an idle instance can become very sluggish. -- 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/-/HW3Anafooa8J. To post to this group, send email to google-appengine-java@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.
[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 way they were before. There's a very good explanation by a Googler in this thread: https://groups.google.com/d/msg/google-appengine/nRtzGtG9790/d0hB-q9__S8J -- 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/-/x0bcMO7McZkJ. To post to this group, send email to google-appengine-java@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.
[appengine-java] Re: Always On not working properly
https://lh3.googleusercontent.com/-HJJBk5I6WUI/TlZvPKlYK_I/ACM/i4WYsSQLoiA/sc.png 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 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/-/0Erv8xtMzj4J. To post to this group, send email to google-appengine-java@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.
[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/google-appengine-java/-/v4njtRVeZYUJ. To post to this group, send email to google-appengine-java@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.
[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.google.com/d/msg/google-appengine-java/-/dZHHrNMWGx8J. To post to this group, send email to google-appengine-java@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.
[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 fixed the problem if it has been known for some time. -- 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/-/ZrRxmkx2B4MJ. To post to this group, send email to google-appengine-java@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.
[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 crappy instance swapping algorithm which indicates that maybe they are trying to cram too many instances into the available physical servers and that this is the reason why there is so much instance swapping going on in GAE. -- 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/-/_HGZWMcIY4oJ. To post to this group, send email to google-appengine-java@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.
