Re: Lag between initialization of call in Gateway and ContractRouter #fabric-chaincode #fabric-sdk-java #hyperledger-fabric
Marek Malik <info@...>
This is exactly the behavior, there is a single request with payload that has for example 146 records. In my service I’m doing 146
'putState' calls to store data to CouchDb.
Od: Matthew White <WHITEMAT@...>
Just to check I understand your situation.
You're submitting a single transaction, that in effect, does a number of 'putState' calls. When that number gets to the ~140 the end-end time has increased.
When you say the payload is 100k, is that of the original transaction, or the data being stored in the states.
How many orgs?
What's the endorsement policy?
Matthew B White IBM Blockchain Solutions Architect
Email me at WHITEMAT@...
Note: restricted availability for meetings 14:30 to 17:00 UK Tuesday
IBM United Kingdom Limited, Hursley Park, Winchester, Hampshire, SO21 2JN
"The wrong answers are the ones you go looking for when the right answers stare you in the face"
Unless stated otherwise above: