I can't speak to the others as I work on Quorum, but there are a few good sources that our team uses and references.
Here is performance evaluation done by an external team with published method and results: https://arxiv.org/abs/1809.03421
Here is one of the tools we use that tries to standardize a way to submit and measure txn throughput in ethereum like ...
I've never used Parity so couldn't really tell. Geth is somewhat easy to use.
After you have decided on the client you have to decide on the node to use. Node relays your commands to the blockchain and keeps the blockchain state. You can either run your own - but you don't have to download the whole blockchain as different clients have different lighter ...
What is the correct way to do this and what are the implications of this?
You have to update the IP in the chain spec or in your bootnodes configuration. Otherwise, Parity won't know the route over IP to the node.
Is it as simple as distributing a new chain specification?
Would this be considered a fork?
No, this only affects the node ...
This is an rpc call that is implemented across clients and I doubt Parity has any plans to deprecate this, as it would break too many application.
There is however a strong desire to stop support for account management and hence most of the rpcs to do with account management have a deprecation notice.
You can view them here: https://github.com/paritytech/...
In addition to the above, it depends on which flavour of PoA you are running.
Clique has determinstic finality and is works off GHOST (Greediest Observed Heavy Subtree). So depending on your trust model, you might want to wait a couple of confirmations.
Aura on the other hands provides finality after a majority vote i.e greater than n/2 validators have ...
Technically you don’t have to .. but those transition numbers indicate when those eips come into play. If you are going to use any of the features then it makes sense to set them to kick in from the beginning.
You also don’t need the dao transition since in your private blockchain the dao never happened
I would suggest first exploring the tx-queue related configuration options. From the Parity documentation:
Maximum amount of memory that can be used by the
transaction queue. Setting this parameter to 0 disables
limiting. (default: 4)
Maximum amount of ...