5 ms·

Are you happy with the performance of AppEngine? I have tried it last summer and was quite disappointed. CPU-bound programs that completed in a few seconds on

• obulpathi 11y ago
  App Engine expects your web apps to return almost immediately (in a matter of few ms). For anything that takes longer, you need to use task queues in App Engine. Or maybe try AppEngine Managed VM's?
  • oaktowner 11y ago
    App Engine requests time out after 60 seconds (that's 60000 ms). https://cloud.google.com/appengine/articles/deadlineexceedederrors https://cloud.google.com/appengine/articles/deadlineexceeded... (I work at Google, but not on App Engine)
    • colonelxc 11y ago
      They don't have to if you use Basic or Manual Scaling (Then they can run up to 24 hours). https://cloud.google.com/appengine/docs/java/modules/#Java_Instance_scaling_and_class https://cloud.google.com/appengine/docs/java/modules/#Java_I... If you run multiple modules at once (some serving the frontend, some for longer tasks w/task queues), you can have the best of both worlds and use different scaling options for each. (I also work at Google, but also not on App Engine)
• boulos 11y ago
  If you like the App Engine model, but want a "full computer worth of horsepower", you might want to consider our "Managed VM" environment built on top of Compute Engine: https://cloud.google.com/appengine/docs/managed-vms/ https://cloud.google.com/appengine/docs/managed-vms/ Disclaimer: I work on Compute Engine.
  • kiennt 11y ago
    Managed VM is still beta, I think only brave one could try beta for production.
    • mvitorino 11y ago
      We have been using Managed VMs in production for while now, integrated in a micro-services architecture, for non-essential, non-frontend services and are quite happy with it. Using custom VMs (Docker based) and work like a breeze.
  • plexicle 11y ago
    I love GCE. I really would like to see Node on it natively, without the need for ManagedVM. I tried it a while ago and did not want to deal with all of the Docker stuff. It was especially a pain on Windows. :(
  • deleted 11y ago
    [deleted]
• ariwilson 11y ago
  Default AppEngine instance is only running at 600MHz. You can choose to pay for a faster instance: https://cloud.google.com/appengine/docs/python/modules/#Python_Instance_scaling_and_class https://cloud.google.com/appengine/docs/python/modules/#Pyth...
• stickfigure 11y ago
  Traditional App Engine is not particularly cost-effective for compute-intensive loads, but it works great for basic web workloads. If you have special needs, Managed VMs have the performance characteristics of the underlying Compute Engine node. We've found that App Engine is not "all or nothing"; it's the backbone of our app but we run services where they make the most sense (usually GCE).
• vgt 11y ago
  In addition to all the excellent comments here. Let's not forget that the massive massive Snapchat runs almost entirely on Google AppEngine. So if AppEngine can handle their scale, it can handle most others :)
  • iampims 11y ago
    No longer true. It's all GCE now last I heard.
    • vgt 11y ago
      Where'd you hear that? Not without risk of giving an argument from authority, your sources are inaccurate. As late as November of last year Snapchat was on stage talking about their broad AppEngine use. (I work on Google Cloud).
      • arouzrokh 11y ago
        +1 App Engine Product Manager here
      • deleted 11y ago
        [deleted]