从 CPU 性能角度来看，Google App Engine 后端的执行时间比非后端的执行时间快多少？
我们正在 Google App Engine 平台上开发一个原型应用程序，但部分代码需要相当密集的 CPU 处理，并且表现出糟糕的性能。我们尝试优化代码，但我们也尝试探索“投入更多硬件”的方法来达到优化目的。 :-)
Google 的官方文档似乎强调了这些功能：后端允许代码执行超过 30 秒并且您可以使用后端拥有永远在线的实例，但没有明确说明我们期望我们的代码能跑多快与使用常规执行相比，非后端，环境。浏览网络也没有多大帮助。
据我所知，使用更高级别的后端（例如B8 类、4.8 GHz 虚拟 CPU）很可能会给我更快的执行时间，但我很好奇（并且充满希望！）即使使用最低级别的后端是否也能给我们更快的执行时间。
因此，我希望 stackoverflow 中的众智者能够分享他们的经验：与非后端环境相比，Google App Engine 的后端在性能方面快了多少？
We are developing a prototype app on top of Google App Engine's platform, but some part of the code requires quite intensive CPU processing and exhibit abysmal performance. We tried to optimize the code, but we are also trying to explore the throw more hardware approach for our optimization purposes. :-)
The official documentation from Google seems to emphasize the features: backend allows code to execute more than 30 seconds and you can have always-on instance using backend, but does not give clear outline on how much faster we could expect our code to execute compared to using a regular, non-backend, environment. Looking around the web does not help much either.
I understand that using the higher classes of backends (e.g. class B8, 4.8GHz virtual CPU) would most likely give me much faster execution time, but I'm curious (and hopeful!) whether even using the lowest class of backend could give us much faster execution time.
So, I'm hoping the crowdwisdom in stackoverflow could share their experience regarding how much faster Google App Engine's backend compared to the non-backend environment, performance-wise?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
几个月后，Google 发布了 App Engine 1.6.1 并将该功能添加到 调整前端实例以使用不同的类，事情变得更加透明。
现在可以得出结论，默认的前端实例相当于一个CPU容量为600MHz的虚拟机。这相当于最低级别后端实例的CPU容量。
因此，与默认的前端实例类相比，即使是最低类的后端实例也不会给我带来性能提升。好处是我们现在可以选择更高级别的前端实例，而不是依赖更高级别的后端来执行 CPU 密集型代码。
Now that we are several months in the future, Google had released App Engine 1.6.1 and adds the capability to adjust frontend instances to use different classes, things has become much more transparent.
It now could be concluded that the default front end instance is equivalent to a virtual machine having CPU capacity of 600MHz. This is equivalent to the CPU capacity of the lowest-class backend instance.
So, even the lowest-class backend instance would not give me a performance boost compared to the default frontend instance class. The good thing is that we now could choose a higher-class frontend instance rather than relying on higher-class backend to execute CPU-intensive code.