Update State Channels
parent
600d113508
commit
4c5e83623f
@ -18,7 +18,7 @@ On one state channel session, you can roughly execute:
|
||||
* 500+ coin transfers per second
|
||||
* 3000+ plain messages per second
|
||||
|
||||
(or a mix of the above). These are estimates based on a rudimentary benchmark suite, running on an M2 Macbook, and can be updated on request. It's important to note that these interactions come with an ordering guarantee, i.e. they are all performed sequentially. Multiple concurrent channels allow for much higher throughput when transactions can be serviced in parallel.
|
||||
(or a mix of the above). These are estimates based on a rudimentary benchmark suite, running on an M4 Macbook, and can be updated on request. It's important to note that these interactions come with an ordering guarantee, i.e. they are all performed sequentially. Multiple concurrent channels allow for much higher throughput when transactions can be serviced in parallel.
|
||||
|
||||
An intuition for the number "500+ coin transfers per second" would be that given that the test measured round-trip time for both parties of a coin transfer (2 ms), one might estimate the processing overhead of serving one side of a State Channel payment to be **less than 1 ms**.
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user