已达到Google App Engine前端实例小时限制 [英] Google App Engine Frontend Instance Hours Limit Reached
问题描述
我有一个由Google App Engine Free选项托管的静态html网站。我没有任何交通可以说，因为它是新的网站，只有流量是我自己访问该网站。
我注意到，只有15个主页请求，我的前端实例消耗的时间是5％。以这个价格，我的网站每天只能为300位访问者提供服务。
我想知道在达到前端实例小时数限制时会发生什么？我的网站将无法公开？我在某处读到静态内容由不同的服务器提供服务，并且应该仍然服务，只要您不超出带宽限制。这是真的吗？
如何减少前端实例小时数？
只是为了澄清一点。你正在考虑每个请求消耗你的免费配额.05 / 15。这是你的根本错误。每个请求都将由您的应用实例提供。您可以免费获得28个实例小时。每次发送请求时，如果没有实例处于活动状态，则会启动一个实例，并且它将占用此配额的15分钟 - 即使它只处理一个请求。但是，如果您的应用程序效率很高，则可以在15分钟内为此一个实例提供数千个请求。如果您的应用程序效率低下，或者您的流量很大，则最终会一次运行多个实例。如果始终有4个实例始终运行，则每15分钟将消耗1小时的实例配额，以便在6小时后您的站点将不可用。如上所述，这是当您开始玩最小/最大空闲实例时 - 您可以为更少的实例权衡响应时间。在这个例子中，假设您调整最小/最大空闲时间并让您的应用程序的响应时间增加，但通过这样做，您可以将活动实例的数量从4减少到1。然后，您可以将该站点保持整整24小时。
I've a static html website hosted with Google App Engine Free option. I do not have any traffic to speak of as it is new site and only traffic is myself visiting the website.
I notice, with just 15 request of the homepage my frontend instance hours consumed is 5%. With this rate, I my website can serve only 300 visitors per day.
I want to know what happens when the frontend instance hours limit is reached? Will my website become unavailable to public? I read somewhere that static content is served by different servers and should still be served, as long as you don't go beyond the bandwidth limits. Is this true?
How to reduce frontend instance hours?
Just to clarify a bit for you. You are thinking each request consumed .05/15 of your free quota. This is your fundamental error. Each request will be served by an instance of your app. You get 28 instance hours free. Each time a request is sent, if no instance is active, one will be started and it will consume 15 minutes of this quota -- even if it just services one request. However, if you app is efficient, many thousands of requests can be served by this one instance in 15 minutes. If your app is inefficient, or you have a lot of traffic, you will end up with more than one instance running at a time. If you always have 4 instances always running, you will consume 1 hour of instance quota each 15 minutes, so your site will become unavailable after 6 hours. As noted, this is when you start playing with the min/max idle instances -- you can tradeoff response time for fewer instances. In the example, let's say you adjust Min/Max Idle and let your app's response time go up, but by doing so you reduced the number of active instances from 4 back to 1. You could then keep the site up for a full 24 hours.
这篇关于已达到Google App Engine前端实例小时限制的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
