mirror of
https://github.com/emmett-framework/granian.git
synced 2025-08-04 17:08:02 +00:00
parent
12a966c1d3
commit
8dc8c01b95
2 changed files with 2 additions and 2 deletions
|
@ -68,7 +68,7 @@ def benchmark(endpoint):
|
|||
# primer
|
||||
wrk(5, 8, endpoint)
|
||||
time.sleep(2)
|
||||
# warmup
|
||||
# warm up
|
||||
wrk(5, max(WRK_CONCURRENCIES), endpoint)
|
||||
time.sleep(3)
|
||||
# bench
|
||||
|
|
|
@ -22,7 +22,7 @@ There are two separate parts to an RSGI connection:
|
|||
- A *connection scope*, like ASGI, which represents a protocol connection to a user and survives until the connection closes.
|
||||
- A *connection protocol* interface the application can interact with, that will responsible of trasmitting data from and to the client.
|
||||
|
||||
Applications are consequentially called and awaited with a connection scope and a connection protocol to interact with. All this happening in an asynchronous event loop.
|
||||
Applications are consequently called and awaited with a connection scope and a connection protocol to interact with. All this happening in an asynchronous event loop.
|
||||
|
||||
Each call of the application callable maps to a single incoming “socket” or connection, and is expected to last the lifetime of that connection plus a little longer if there is cleanup to do.
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue