Server Errors - Timeouts. Free accounts getting inferior service?

[David Manns]

This morning (and many times over recent weeks) my application, which normally runs perfectly, encounters both very slow response times as well as these server errors.  When I look at the logs, the errors are timeouts.  The application uses the web2py framework.  The problem occurs both on the initial screen either a login screen or a search form, depending on whether a persistent login has been used - in either case no datastore access, and at random times during a sequence of searches and edits of the database.

Perhaps related to business hours, often works more consistently off peak hours.  Are free applications now being discriminated against and being relegated to a small group of, at times, overloaded servers?

[Brandon Wirtz]

If you get 12 requests in 1 second, you now only have 1 instance, the free service used to spin up additional instances and you were billed for CPU time. As a result you used to be able to have 12 instances actually only bill for 1 instance worth of CPU a day, (if they were waiting for things to happen for example)

 

Likely you have users hitting your app, asking for 8 things at once, and when you get 3 people at the same time, your instance can’t serve all of them before they time out.

--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/JZ8nA4_ZqlsJ.
To post to this group, send email to google-a...@googlegroups.com.
To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.