Ensure jsonrpc threading settings are sane (#11267)
* Ensure jsonrpc threading settings are sane Starting with `jsonrpc` v14, the "server threads" setting is more important than before and the current default of 1 means the https server is effectively single-threaded. This PR proposes a new default of 4 (and ensures that crazy settings like e.g. `0` are bumped to at least `1`). Also included: some docs, tests and cosmetics. * Update parity/rpc.rs Co-Authored-By: Tomasz Drwięga <tomusdrw@users.noreply.github.com> * Update parity/rpc.rs Co-Authored-By: Tomasz Drwięga <tomusdrw@users.noreply.github.com> * Remove (i.e. deprecate) `--jsonrpc-threads` command line option * Call numbers NUM * Don't show a default for --jsonrpc-threads (deprecated) * Show deprecation warning when using `--jsonrpc-threads` or `processing_threads` * Update parity/deprecated.rs Co-Authored-By: Niklas Adolfsson <niklasadolfsson1@gmail.com> * Fix test * Fix tests for real
This commit is contained in:
@@ -31,6 +31,7 @@ origins = ["none"]
|
||||
[rpc]
|
||||
disable = true
|
||||
port = 8180
|
||||
server_threads = 13
|
||||
|
||||
[ipc]
|
||||
apis = ["rpc", "eth"]
|
||||
|
||||
Reference in New Issue
Block a user