Timeline for How many concurrent requests can an Ethereum node handle?
Current License: CC BY-SA 3.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 5, 2018 at 15:49 | answer | added | antikantian | timeline score: 4 | |
| S Sep 4, 2017 at 10:47 | history | bounty ended | q9f | ||
| S Sep 4, 2017 at 10:47 | history | notice removed | q9f | ||
| Sep 1, 2017 at 19:24 | comment | added | Thomas Jay Rush | It could be interpreted as number of transactions. When I first clicked on it, that's what I thought. No biggy though. | |
| Aug 31, 2017 at 23:23 | comment | added | Thomas Clowes | The question seeks to discern how many requests a node can process concurrently. The most common interface to a backend node is RPC. I am not clear as to where the confusion lies but am happy to change it if others see fit. | |
| Aug 31, 2017 at 21:05 | comment | added | Thomas Jay Rush | The title should be improved. I think the question is about RPC requests, but the title leads one to think it's about processing transactions under consensus. The answer to that question is however many fit under the block-wide gasLimit. | |
| Aug 31, 2017 at 20:09 | answer | added | Thomas Jay Rush | timeline score: 2 | |
| S Aug 31, 2017 at 9:17 | history | bounty started | q9f | ||
| S Aug 31, 2017 at 9:17 | history | notice added | q9f | Reward existing answer | |
| Aug 31, 2017 at 9:08 | answer | added | tayvano | timeline score: 11 | |
| Aug 29, 2017 at 10:23 | answer | added | q9f | timeline score: 3 | |
| Aug 7, 2017 at 19:04 | answer | added | lungj | timeline score: 1 | |
| Jul 27, 2017 at 21:56 | history | asked | Thomas Clowes | CC BY-SA 3.0 |