ExternalVendorCode/corda
1
0
Fork 0
mirror of https://github.com/corda/corda.git synced 2025-06-01 23:20:54 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

ENT-1951 Storage usage from performance tests (#1216)

Browse Source 
* ENT-1951 Storage usage from performance tests

* Qualify database used

* Review feedback
This commit is contained in:
Rick Parker 2018-07-06 11:01:45 +01:00 committed by GitHub
parent 431538cc31
commit d03f31e178
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/source/sizing-and-performance.rst
View File

@ -133,6 +133,14 @@ here to a minimum, without resorting to any extreme measures, by keeping them in
databases separated from the node with increased latency (high single digit, low double digit millisecond - effectively cross region) and it databases separated from the node with increased latency (high single digit, low double digit millisecond - effectively cross region) and it
significantly impacts performance, with flows taking much longer to complete and overall throughput reduced accordingly. significantly impacts performance, with flows taking much longer to complete and overall throughput reduced accordingly.
Database storage
~~~~~~~~~~~~~~~~
In our performance tests, on **Microsoft SQL Server 2017**, we see database table space usage of around 10KB per state with an additional 10KB per transaction. So a transaction with
3 output states would use 10KB + (3 x 10KB) = 40KB of storage. This will obviously vary dependent on the complexity of the states and the extent to which they
implement vault schema mappings, and is something that is likely to be changed in future releases as we finesse transaction storage in the light of
performance and privacy requirements.
Scaling with CPU core count Scaling with CPU core count
--------------------------- ---------------------------