Thanks for the responses both.
@alexander.sherbakov - My local Indy setup is quite simple: 1 Ubuntu 14.04 VM contains 4 ledger nodes (https://github.com/bcgov/von-network) and a second Ubuntu 14.04 VM (in the same network) fires read/write transactions (latest version of indy-sdk via node.js wrapper). Network latency between the ledger nodes themselves should be minimal/zero since they are on the same VM. Read transactions appear to be signed by 3 of the 4 ledger nodes.
@danielh - *“It sounds like you are having to collect read responses from multiple nodes and confirm that they agree, instead of reading a single response that includes a state proof to short-circuit the consensus check”
In my setup the reads do bounce between 3 of the 4 ledger nodes (editing the poolconfig to contact fewer nodes for a read doesn’t change that). For a write, do you know if the consensus process is concluded before the state proof is sent back?
Nevertheless, my assumption is that the write+consensus process should be slower than a single read bounced between a few nodes…