Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Test Steps & Test Data

  1. Create Dataspace: curl -u cpsuser:cpsr0cks! -X POST "http://localhost:8883/cps/api/v1/dataspaces?dataspace-name=openroadm" -H "accept: text/plain" -d ''
  2. Create Schemaset:  curl -u cpsuser:cpsr0cks! -X POST "http://localhost:8883/cps/api/v1/dataspaces/openroadm/schema-sets?schema-set-name=owb-msa221-schema" -H "accept: text/plain" -H "Content-Type: multipart/form-data" -F 'file=@owb-msa221.zip;type=application/zip'   Schemaset: owb-msa221.zip
  3. Create Anchor: curl -u cpsuser:cpsr0cks! -X POST "http://localhost:8883/cps/api/v1/dataspaces/openroadm/anchors?schema-set-name=owb-msa221-schema&anchor-name=owb-msa221-anchor" -H "accept: text/plain" -d '' 
  4. Post the initial Node: 
    curl -g -H "Authorization: Basic Y3BzdXNlcjpjcHNyMGNrcyE=" -H "Content-Type: application/json" --request POST 'http://localhost:8883/cps/api/v1/dataspaces/openroadm/anchors/owb-msa221-anchor/nodes' -d @owb-msa22-first-node-payload.json -i  Test data: owb-msa22-first-node-payload.json
  5. Use Test client to post multiple data concurrently. Test data:  msa221-data.zip

Write Test Cases

Test Iteration 1 - 4 GB RAM, 2 vCPU - Kubernetes Cluster

...

#

#Nodes

ThreadTime taken to post single nodeTime taken to post all data nodesComments
1100011.8 - 2 sec30 m 15 sec
210002 1.8 - 2 sec29 m 49 secNo improvements in performance with increased threads count

310005 1.8 - 2 sec30m 44 sec
4100010 1.8 - 2 sec30m 21 sec
520001 1.8 - 2 sec59 m 26 sec
630001 1.8 - 2 sec1h 30 min 29 sec

Read Test Cases

See Reading Large Data Instrumentation Comparisons

Test Results (After xpath query performance improvements)

No of nodesthreads countTime to read single txnTime to read allComments
5001~0.5 sec4 min 10 secDrastic improvement in performance than before. It took 2 hours to retrieve the data before the fix.
5002~0.5 sec4 min 12 secNo improvements in performance with increased threads count