GAE定价：永远在功能和实例收费 [英] GAE Pricing: Always On feature and instances charging

问题描述

有些东西我真的没有得到关于新的定价。据我所知，我现在计算（例如）实例/小时的数量。另一方面，后来我选择了永远在线功能，从那时起，我的应用程序总共运行了3个Resident实例。

现在，A.F.A.I.C.S.在旧的定价模式中，我使用CPU时间收费的那个，永远在线功能非常好，不仅使应用程序响应更快，而且由于实例不再启动/被破坏，当交通稀少时，CPU时间被降低（事实上，这可以在仪表板上看到）。

但现在，由于我按Instance / hours计费，即使这些实例实际上没有做任何事情（仅仅因为它们就在那里，总是在），我有这个永远在线选项的事实实际上并没有为我的账单增加很多钱？

我在问这个问题，因为自从新的定价模式被激活后，我的前端实例小时（现在是过去9小时的29.21）有了大幅增加，其中之前的CPU时间从来没有真正接近于免除配额的限制。

解决方案

添加了很多甚至当这些事件实际上没有做任何事情（仅仅因为他们只是在那里，总是在），为我的账单增加了很多钱，即使这些事例实际上没有做任何事情...... p>

问题是他们正在做某件事情。他们占用内存。新的定价模式试图更准确地模拟谷歌的基础成本，或者至少这是他们告诉我们的。您可以通过转到管理界面来更改总有多少实例。如果你没有真正使用全部3个，请尝试下降到2或1.如果你的流量高峰，更多的实例将启动。您还可以设置一个值，让您在新实例加速前希望用户能够承受多少延迟。

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.

解决方案

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)?add a lot of money to my bill, even when those instances are not actually doing anything ...

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.

这篇关于GAE定价：永远在功能和实例收费的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！