multithreading - How does Go handle concurrent request on Google App Engine -


I'm a little confused about how I run concurrent requests on Google App Engine. That's why I am hoping someone can provide some clarity.

This is the fact that I have assembled:

  1. Go to App Engine is threaded single -

  2. <
  3. If there is a single threaded app engine on the go then there is a 3 point seal. It leaves 1 and 2. If the app goes to the engine then there is a threaded and requires threads to continue execution while blocking for I / O, so it seems that while waiting on an app engine go installation I / O, all the gorants Will block.

    Is that correct? If not, does con's concomitant actually work on app engine?

    To help me measure things, if I had to keep a connection open for 30 seconds

    Edit: This feature is requested which Go Instance from 10 Will allow more concurrent requests to be handled. . Please star it.

    An app app engine example allows for 10 concurrent requests, but only runs a CPU thread , Multiple requests can be processed simultaneously, but only CPU will be able to work at the same time. If there is a request, say, waiting for the return of the Datastore API call, another request is free to process by the same example.

    Your statement "If the go engine is single threaded on the engine, then point 3 is controversial." There is still a limit of 10 concurrent in-flight requests for a single go app engine, for example. While talking about "threads", the documentation becomes slightly loose with words.

Comments

Popular posts from this blog

Python SQLAlchemy:AttributeError: Neither 'Column' object nor 'Comparator' object has an attribute 'schema' -

java - How not to audit a join table and related entities using Hibernate Envers? -

mongodb - CakePHP paginator ignoring order, but only for certain values -