Load and Performance Info
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

 
$
%
123
 
 
 
 
 
 
 
 
 
ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
Requirement from INDY-1343
Acceptance Criteria
Perform a test of an Indy network that has the following attributes:

The ledger is pre-loaded with 1 million transactions
Pool size at least matches the number of network nodes initially expected in the Sovrin network (currently 25 nodes).
1K concurrent clients
Over a 3 hour period induce a sustained throughput of 10 write transactions per second and 100 read transactions per second on average.
Write load is a mixture of:
writing credentials schema (5%),
writing credential definition (5%)
revoke registry definition (5%)
revoke registry update (5%)
write DID to ledger (20%)
write payment to ledger (45%)
write attrib to ledger (15%)
Read load is a mixture of:
read DID from ledger (45%)
read credential schema (10%)
read credential definition (10%)
read revoke registry definition (10%)
read revoke registry delta (10%)
read attrib from ledger (10%)
read payment balance from ledger (5%)
Write response time should be less that 5 seconds (would also like a report of the average).
Read response time should be less than 1 second (would also like a report of the average).



2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
Key Metrics
Logging enabled at INFO
View change enabled
21
22
Build
1.5.551 | 1.6.1~655
1.6.726 | 1.6.8~881
23
Date9-Aug-201818-Dec-2018
24
Pre-loaded ledger size
Req: 1 million txns
25
Number concurrent connections
Req: 1,000 concurrent connections
100 writing
900 reading
100 writing
900 reading
26
Writes / second
Req: Sustain 10 / second
9 - 1110
27
Reads / second
Req: 100 reads/sec
1701000
28
Sustained Load Time
Req: sustain 3 hours
940 - 45
29
Write repsonse time less than 5 seconds
30
Read response time less than 1 second
31
Token
48k payment write transactions
32
Token
10k payment write txns in 40 minutes (4 token txns / second)
33
Points of Consensus Loss
Max numbers resulting in loss of consensus
34
Ledger size causing consensus loss
35
Number of concurrent connections resulting in consensus loss
36
Number of reads resulting in consensus loss
37
Number of nodes in pool resulting in consensus loss
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
Loading...