Greetings Kaan, You have brought up concerns in the past over how we handle this group, so I want to share some improvements with you and thank you for your part in inspiring them.
- In the interest of reducing confusion about where to post, we have updated our help center documentation <https://support.google.com/cloud/answer/3466163?hl=en&ref_topic=3340599> and welcome message <https://groups.google.com/forum/#!forum/google-appengine> to better enumerate your community support options. Note also that pinned threads referring to StackOverflow have vanished. - We've asked the support staff to change their display names on this forum to follow the pattern "Bob (Google Cloud Support)." This, hopefully, will make it more obvious when one of my colleagues' requests for information is motivated by Google's desire to provide support here. - In order to prevent the appearance of censorship, I've asked the support staff to reserve the use of moderation powers for only the most extreme circumstances, such as when a certain Italian-speaking user shares his political opinions. - Finally, in order to foster a sense of community we have re-organized how Support assigns itself to groups. You'll find that a few Support Team members <https://groups.google.com/forum/#!aboutgroup/google-appengine> who have concentrated on this group are now nearly as active as yourself. Regards, Jesse P.S. Another of my colleagues on the team will be following up on some specific points you made in part 2 of your mail. On Tuesday, May 26, 2015 at 4:57:06 AM UTC-4, Kaan Soral wrote: > > I've been using App Engine for probably something like 5 years, I have one > major app that has been running for 5 years, it's very well polished, and > the traffic and behaviour of the app is very predictable *knocking on wood* > I have another app that I've been working on for 3 years, it didn't take > off yet, the new app is unpredictable in behaviour, it's vast and > unthrottled > > While the old app has been handling millions of requests without errors > and issues, the new one is failing on even the simplest tasks, the logs are > filled with TransientError's, instance failures, transaction failures, the > whole thing is chaotic > > The old app has throttled queues and basic tasks, the throughput is well > calibrated to complete all the tasks in 5 hours, using optimal amount of > instances, the traffic is regular, it eases in and eases out throughout the > day (without throttling, the old app was in similar state before) > The new app is built to perform, so it's queues have no limits, it trusts > App Engine to scale as much as it can > > Well turns out that trust isn't well placed, App Engine is supposed to > scale on it's own, yet when you leave the limits to the App Engine, it > fails to perform > You might ask: "Why would I use App Engine if I'm going to manually scale > the limits myself?" - That's a good question, If you're going to have to > adjust the limits and throughput manually while your app grows, you might > as well use AWS or a similar more reliable service > > This is mostly a rant post, but the advice is still solid, one has to > manually calibrate the throughput of routines to prevent app spikes, the > instance births and deaths should always be eased in and eased out, > otherwise various services of app engine fail to perform > On the bright side, throttling also reduces the costs significantly, so > it's a good idea to always keep an eye on the app and manually calibrate > all routines - on the other side, if your app gains additional traffic > without your supervision, these routines will hog and halt > > ------ > > On a more technical side, some of these errors are: > "Request was aborted after waiting too long to attempt to service your > request." - they come in 100's - flood the logs - these are taskqueue > push tasks, so the error is pretty stupid, if they can't be handled, they > should be left in the queue > "google.appengine.api.taskqueue.taskqueue.TransientError" - these are > from pull queues, there are invisible/untold limits of pull queues, this is > also very concerning, because if your app grows, your scale might be bound > by these limits, so try not to use pull queues too much > "DeadlineExceededError's" - these are pretty random and rare, yet when > you run thousands of tasks, you get these in your logs, they might be > omitted > Transactions errors and anomalies: these used to happen a lot, but I > switched to a pull queue based logic to prevent them, now they are replaced > by pull queue anomalies > > (It would have been great if limits and capacities of each service was > more transparent, and I really think taskqueues need some eased bucket > configurations, things that will help task batches to be executed in an > eased manner, currently the only way to achieve this is to put flat and low > throughput limits - similarly, same kind of control can be achieved on the > instance scheduler level) > > ------ > > Also, after 5 years, I gave up on app engine support, during a time we > used to get actual support from this google groups, currently it's just > random initial replies and no follow ups, so unless you are paying $500 or > something monthly for support, don't expect much support, you are on your > own to detect the issues and prevent them through experimentation and > volunteer help > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/922d1ba3-6fb3-46c4-930e-6a69b94f97da%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
