如何在应用引擎上计算前端实例小时数？

问题描述

我有一个简单的在线订购应用程序。它可能每周处理25个小时，其中大部分是周一和周二。

查看仪表板，我看到：

 结算状态：免费 - 设置配额每24小时重置一次。下一次重置：7小时
资源使用情况
前端实例小时数16％28.00实例小时数4.53 
  

4.53小时对于我拥有的用户数似乎非常高。

我的一些页面调用存储在另一个服务上的文件数据库数据库， ：

  URI请求MCycles延迟
 / profile 50 74 1241 ms 
 / order 49 130 3157 ms 
  

我的身份验证页面在向第三方发出通知时也有很高的延迟：

  / auth / google / callback 9 51 2399 ms 
  

我仍然没有看到它们的总和可以达到4.53小时吗？

任何人都可以解释吗？

解决方案

每次实例出现问题时，您都会收取15分钟的费用。

，但是它们被隔开，你的实例会关闭，并且在下一次实例启动时，你会收到15分钟的费用。

你可以轻松地将4.5实例小时数18个HTTP请求。

I have a simple online ordering application I have built. It probably handles 25 hours a week, most of those on Mondays and Tuesday.

Looking at the dashboard I see:

Billing Status: Free - Settings Quotas reset every 24 hours. Next reset: 7 hrs
Resource             Usage
Frontend Instance Hours      16%     4.53 of 28.00 Instance Hours

4.53 hours seems insanely high for the number of users I have.

Some of my pages make calls to a filemaker database stored on another service and have latencies like:

URI         Reqs        MCycles     Latencies
/profile    50          74          1241 ms
/order      49          130         3157 ms

my authentication pages also have high latencies as they call out to third parties:

/auth/google/callback 9  51  2399 ms

I still don't see how they could add up to 4.53 hours though?

Can anyone explain?

解决方案

You're charged 15 minutes every time an instance is spins up.

If you have few requests, but they are spaced out, your instance would shut down, and you'll incur the 15 minute charge the next time the instance spins up.

You could easily rack up 4.5 instance hours with 18 HTTP requests.

这篇关于如何在应用引擎上计算前端实例小时数？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！