GAE 定价：Always On 功能和实例收费
对于新的定价，我确实有些不明白。据我所知，我现在按“实例/小时”数计费（除其他外）。另一方面，不久前我选择了“始终开启”功能，从那时起，该功能实际上使我的应用程序的 3 个“常驻”实例始终运行。
现在，AFAICS，在旧的定价模型中，即我按使用的 CPU 时间收费的模型，“始终开启”功能非常棒，它不仅使应用程序响应更快，而且由于实例不再启动/torn-down 当流量稀缺时，CPU 时间会降低（实际上这在仪表板上可见）。
但现在，由于我是按实例/小时计费的，事实上，我激活了这个“始终开启”选项并没有给我的账单增加很多钱，即使这些实例实际上没有做任何事情（只是因为它们就在那里，永远在线）？
我问这个问题是因为自从激活新的定价模型以来，我的前端实例小时数大幅增加（现在过去 9 小时为 29.21），而在此之前 CPU 时间从未真正接近过免费配额。
There's something I really don't get about the new pricing. As far as I can see, I am now billed (amongst others) for the number of "instance/hours". On the other hand, a while back I've opted for the "Always on" feature, which since then effectively has 3 "Resident" instances of my application always running.
Now, A.F.A.I.C.S. , on the old pricing model, the one where I was charged by CPU Time used, the "always on" feature was great, not only did it made the app more responsive, but since the instances were no longer started-up/torn-down when traffic was scarce, the CPU Time was lowered (and indeed this is visible on the dashboard).
But now, since I'm billed by Instance/hours, the fact that I have this "always on" option active doesn't in fact add a lot of money to my bill, even when those instances are not actually doing anything (simply because they're just there, always on)?
I'm asking this because since the new pricing model was activated, I have whopping increase in Frontend Instance Hours (right now it's 29.21 for the last 9 hours), where before the CPU Time never really came close to depassing the free quota.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
自 1.6.0 起，“始终开启”功能不存在。等效的替代方法是在管理控制台的应用程序设置中将“最小空闲实例”滑块设置为 3（并将“最大空闲实例”保留为“自动”）。
The "Always On" feature does not exist as of 1.6.0. The equivalent replacement is setting the Min Idle Instances slider to 3 (and leaving the Max Idle Instances at "Automatic") in your Application Settings in the Admin Console.
问题是他们正在做某事。他们正在占用内存。新的定价模型试图更准确地模拟谷歌的潜在成本，或者至少他们是这么告诉我们的。您可以通过进入管理界面来更改始终开启的实例数量。如果您并没有真正使用全部 3 个实例，请尝试减少到 2 个或 1 个。如果您的流量激增，则会启动更多实例。您还可以设置一个值，指定在新实例启动之前您希望用户忍受的延迟时间。
The problem is that they are doing something. They are occupying RAM. The new pricing model attempts to more accurately model the underlying costs to Google, or at least that's what they tell us. You can change how many instances are always on by going to the admin interface. If you aren't really using all 3, try going down to 2 or 1. If your traffic spikes, more instances will be started up. You can also set a value for how much latency you want users to endure before new instances are spun up.
调度程序可能会启动多个实例来响应线程。
这是Java中的吗？您可以尝试使其成为线程化的，以使其对较低延迟的响应更加灵敏。
您还可以调整调度程序参数以阻止它启动更多实例。
The scheduler might be spinning up more than one instance to respond to threads.
Is this in Java? You could try to make it threaded, to make it more responsive to lower latency.
You could also tweak the scheduler parameters to discourage it from spinning up more instances.