Clarified the difference between invoke.ts and invoke2.ts

Author: cgorenflo

README.md

@@ -38,6 +38,6 @@ To shut down all Fabric nodes run `terminate_benchmark.sh`
 All following steps use scripts from the  `fabric/fastfabric/scripts/client` folder.
 
 - First run `node addToWallet.js` to copy the necessary user credentials from the `crypto-config` folder into the `wallet` folder.
-- Compile either the `invoke.ts` or `invoke2.ts` script to Javascript (change the `include` line in `tsconfig.json`). See https://code.visualstudio.com/docs/typescript/typescript-compiling for help.
+- Compile either the `invoke.ts` (a client that endorses and submits transactions in one go) or `invoke2.ts` script (a client that first caches all endorsements before submitting them in bulk to the ordering service) to Javascript (change the `include` line in `tsconfig.json`). See https://code.visualstudio.com/docs/typescript/typescript-compiling for help.
 - Depending on your choice modify `run_benchmark.sh` to either run `invoke.ts` or `invoke2.ts`. Run it with the command `.\run_benchmark.sh [lower thread index] [upper thread index exclusive] [total thread count] [endorser addr] [number of touched accounts] [percentage of contentious txs]`. This allows to create multiple client threads on multiple servers (wherever this script is executed), to generate load.
 Example: `./run_benchmark.sh 0 10 50 localhost 20000 70`. This spawns 10 threads on this server (and expects that the script is run on other servers to spawn 40 more threads) and calls an endorser on localhost to endorse the transactions. Because only a fifth of the total threads are spawned by this script, only the first fifth of the accounts are touched, in this case `account0` to `account3999` for a total of 2000 transactions. There is a 70% chance that any generated transaction touches `account0` and `account1` instead of a previously untouched pair to simulate a transaction conflict.