docs: update schema and setup documentation

Author: bitjson

README.md

@@ -23,10 +23,10 @@ To deploy Chaingraph locally, see the instructions in the [Contributing Guide](.
 
 ### Create a Cluster
 
-As of late 2021, DigitalOcean is the most cost-effective cloud provider for Chaingraph deployments (differentiated primarily by pricing of egress bandwidth and persistent volume SSD storage).
+As of 2023, DigitalOcean is the most cost-effective cloud provider for Chaingraph deployments (differentiated primarily by pricing of egress bandwidth and persistent volume SSD storage).
 
-To set up a new cluster, **consider using [Chaingraph's referral code for a $100
-credit](https://m.do.co/c/522a68c96ba3)** (supports `demo.chaingraph.cash`); this should cover a production-ready BCH mainnet deployment for ~30 days (approximately $85/month for SSD storage, one $10/month droplet, and $10/month for the load balancer and egress bandwidth).
+To set up a new cluster, **consider using [Chaingraph's referral code for a $200
+credit](https://m.do.co/c/cb25573fbfe7)** (supports `demo.chaingraph.cash`); this should cover a basic, production-ready BCH mainnet deployment for ~60 days (approximately $85/month for SSD storage, one $12/month droplet, and $12/month for the load balancer and egress bandwidth).
 
 Whichever cloud provider you choose, for the below testnet deployment, provision at least 1 Kubernetes node of the least expensive type.
 
@@ -44,7 +44,7 @@ If you have previously added the `bitauth` repo, run `helm repo update` to fetch
 
 ### Deploy a Release
 
-Using the default configuration, Chaingraph will be installed with a single `testnet4` [BCHN](https://gitlab.com/bitcoin-cash-node/bitcoin-cash-node) full node, an internally-managed Postgres instance, and no load balancer.
+Using the default configuration, Chaingraph will be installed with one `chipnet` and one `testnet4` [BCHN](https://gitlab.com/bitcoin-cash-node/bitcoin-cash-node) full node, an internally-managed Postgres instance, and no load balancer.
 
 This is an ideal configuration for experimenting with Chaingraph, as it can be deployed on very low-powered clusters (often even within the free tier provided by many cloud Kubernetes providers). See the [chart readme](./charts/chaingraph/readme.md) for information about other options.
 

charts/chaingraph/readme.md

@@ -21,7 +21,7 @@ Chaingraph currently supports internal management of mainnet and testnet BCHN no
 A [BCHN](https://bitcoincashnode.org/) node configured to connect to `mainnet` is disabled by default. It can be enabled with the following option:
 
 ```sh
---set bitcoinCashNode.enable=true # --set postgres.volumeSize=625Gi
+--set bitcoinCashNode.enable=true # --set postgres.volumeSize=730Gi
 ```
 
 When enabling mainnet, ensure the volume assigned to Postgres is large enough to hold the database with additional space for indexing (see [Approximate Space Usage](../../docs/schema.md#approximate-space-usage)). If using the internally-managed Postgres instance, this can be configured with the `postgres.volumeSize` value. (See also: [Expanding Volumes](#expanding-volumes).)
@@ -158,7 +158,7 @@ spec:
   - ReadWriteOnce
   resources:
     requests:
-      storage: 625Gi # <- edit this value
+      storage: 730Gi # <- edit this value
 ```
 
 If the specified volume size is larger than the existing volumes, the volumes will be automatically expanded by supporting Kubernetes systems. (Note: volume sizes cannot be reduced using this method.)

docs/schema.md

@@ -51,31 +51,31 @@ Multi-node, multi-chain deployments share common history, so only divergent bloc
 
 This section is periodically updated to provide approximate storage usage information for all default tables and indexes. Actual storage usage will be affected by file system compression and Postgres vacuuming progress. (Vacuuming frees wasted space in the database, so storage usage will fall in the hours/days after initial sync as the database reclaims unused space. The Postgres `VACUUM FULL` command locks the table and performs this compression immediately.)
 
-The below table is derived from the [`/space` view in `pgHero`](../.github/CONTRIBUTING.md#using-pghero) on a recently-vacuumed Chaingraph Postgres database synced with only a single, mainnet BCH node.
+The below table is derived from the [`/space` view in `pgHero`](../.github/CONTRIBUTING.md#using-pghero) on a recently-synced Chaingraph Postgres database with a single, mainnet BCH node.
 
-_**Last Update**: 2021-11-11_
+_**Last Update**: 2023-01-23_
 
 | Relation                      | Size               |
 | ----------------------------- | ------------------ |
-| input                         | 176 GB             |
-| output                        | 100 GB             |
-| output_pkey                   | 78.3 GB            |
-| spent_by_index                | 52 GB              |
-| transaction                   | 35.3 GB            |
-| input_pkey                    | 32.2 GB            |
-| transaction_hash_key          | 24.8 GB            |
-| output_search_index           | 19.7 GB            |
-| block_transaction             | 16.9 GB            |
-| block_transaction_pkey        | 10.9 GB            |
-| block_inclusions_index        | 7.26 GB            |
-| transaction_pkey              | 7.25 GB            |
-| block                         | 131 MB             |
-| block_hash_key                | 52.9 MB            |
-| node_block                    | 33.5 MB            |
-| node_block_pkey               | 21.5 MB            |
-| block_height_index            | 15.3 MB            |
-| block_internal_id_key         | 15.3 MB            |
-| block_pkey                    | 15.3 MB            |
+| input                         | 189 GB             |
+| output                        | 108 GB             |
+| output_pkey                   | 84.2 GB            |
+| spent_by_index                | 56.3 GB            |
+| transaction                   | 37.2 GB            |
+| input_pkey                    | 33.6 GB            |
+| transaction_hash_key          | 26.1 GB            |
+| output_search_index           | 20.7 GB            |
+| block_transaction             | 17.8 GB            |
+| block_transaction_pkey        | 11.5 GB            |
+| block_inclusions_index        | 7.64 GB            |
+| transaction_pkey              | 7.64 GB            |
+| block                         | 168 MB             |
+| block_hash_key                | 67.9 MB            |
+| node_block                    | 44.2 MB            |
+| node_block_pkey               | 32.1 MB            |
+| block_internal_id_key         | 19.9 MB            |
+| block_pkey                    | 19.9 MB            |
+| block_height_index            | 19.1 MB            |
 | node                          | 16 KB              |
 | node_internal_id_key          | 16 KB              |
 | node_name_key                 | 16 KB              |
@@ -87,9 +87,9 @@ _**Last Update**: 2021-11-11_
 | node_block_history            | varies<sup>3</sup> |
 | node_block_history_pkey       | varies<sup>3</sup> |
 
-- Average Transactions Per Day (Jan - Nov 2021): **~168,000 transactions/day**
-- Average Transaction Size (Jan - Nov 2021): **439 bytes**
-- Average Transaction Throughput Per Day (Jan - Nov 2021): **~74 MB**
+- Average Transactions Per Day (Jan 2023): **~12,000 transactions/day**
+- Average Transaction Size (Jan 2023): **838 bytes**
+- Average Transaction Throughput Per Day (Jan 2023): **~10 MB**
 
 <details><summary>SQL</summary>
 

package.json

@@ -47,6 +47,7 @@
     "dev-cluster:upgrade:local": "yarn dev-cluster:upgrade:local-postgres --set bitcoinCashNodeTestnet.enable=false --set bitcoinCashNodeChipnet.enable=false",
     "dev-cluster:bchn:sh": "echo 'Some useful commands:\n\n chain info>> bitcoin-cli -datadir=/data getblockchaininfo\n peer versions>> bitcoin-cli -datadir=/data getpeerinfo | grep subver\n quit>> exit\n' && kubectl exec bitcoin-cash-node-0 -it -- /bin/bash",
     "dev-cluster:bounce:postgres": "yarn dev-cluster:spin-down:postgres && kubectl rollout status statefulset/postgres && yarn dev-cluster:spin-up:postgres",
+    "dev-cluster:prod-sim:restart:agent": "echo 'Restarting chaingraph-agent - the existing pod will begin shutdown, and a new pod will be created immediately. If both are logging to the same file, the logs may overlap momentarily.' && kubectl rollout restart deployment chaingraph-agent",
     "dev-cluster:spin-down:bchn:mainnet": "kubectl scale statefulsets bitcoin-cash-node --replicas=0",
     "dev-cluster:spin-up:bchn:mainnet": "kubectl scale statefulsets bitcoin-cash-node --replicas=1",
     "dev-cluster:spin-down:bchn:testnet": "kubectl scale statefulsets bitcoin-cash-node-testnet --replicas=0",
@@ -79,10 +80,10 @@
     "dev-cluster:hasura:console:prod-sim": "cd images/hasura/hasura-data && hasura console --console-port=8013 --api-port=31933 --endpoint=http://localhost:31933/ --admin-secret=$(yarn dev-cluster:secret:hasura-admin-secret-key)",
     "dev-cluster:hasura:init-migrations": "cd images/hasura/hasura-data && hasura migrate create 'init' --from-server --admin-secret=$(yarn dev-cluster:secret:hasura-admin-secret-key)",
     "dev-cluster:hasura:squash-migrations": "cd images/hasura/hasura-data && hasura migrate squash --admin-secret=$(yarn dev-cluster:secret:hasura-admin-secret-key)",
-    "local:bchn:mainnet": "bitcoin-bchn -datadir=$PWD/data/bchn-local",
-    "local:bchn:pruned": "bitcoin-bchn -datadir=$PWD/data/bchn-local-pruned",
-    "local:bchn:testnet": "bitcoin-bchn -datadir=$PWD/data/bchn-testnet-local",
-    "local:bchn:chipnet": "bitcoin-bchn -datadir=$PWD/data/bchn-chipnet-local",
+    "local:bchn:mainnet": "bitcoin-bchn -datadir=$PWD/data/bitcoin-cash-node-local",
+    "local:bchn:pruned": "bitcoin-bchn -datadir=$PWD/data/bitcoin-cash-node-pruned-local",
+    "local:bchn:testnet": "bitcoin-bchn -datadir=$PWD/data/bitcoin-cash-node-testnet-local",
+    "local:bchn:chipnet": "bitcoin-bchn -datadir=$PWD/data/bitcoin-cash-node-chipnet-local",
     "local:postgres": "postgres -D $PWD/data/postgres-local",
     "local:postgres:init": "bash -c 'initdb --username=chaingraph --auth=scram-sha-256 --pwfile=<(echo \"very_insecure_postgres_password\") --no-locale --encoding UTF-8 $PWD/data/postgres-local'",
     "local:postgres:tune": "yarn local:postgres:psql -c \"ALTER SYSTEM SET shared_buffers = '2048MB'\" && yarn local:postgres:psql -c \"ALTER SYSTEM SET effective_cache_size = '6144MB'\" && yarn local:postgres:psql -c \"ALTER SYSTEM SET maintenance_work_mem = '128MB'\" && yarn local:postgres:psql -c \"ALTER SYSTEM SET checkpoint_completion_target = '0.9'\" && yarn local:postgres:psql -c \"ALTER SYSTEM SET min_wal_size = '4GB'\" && yarn local:postgres:psql -c \"ALTER SYSTEM SET max_wal_size = '16GB'\" && yarn local:postgres:psql -c \"ALTER SYSTEM SET default_statistics_target = '500'\" && yarn local:postgres:psql -c \"ALTER SYSTEM SET random_page_cost = '1.1'\" && yarn local:postgres:psql -c \"ALTER SYSTEM SET max_connections = '50'\" && yarn local:postgres:psql -c \"ALTER SYSTEM SET work_mem = '8MB'\" && yarn local:postgres:psql -c \"ALTER SYSTEM SET max_worker_processes = '8'\" && yarn local:postgres:psql -c \"ALTER SYSTEM SET max_parallel_workers_per_gather = '4'\" && yarn local:postgres:psql -c \"ALTER SYSTEM SET max_parallel_workers = '8'\" && yarn local:postgres:psql -c \"ALTER SYSTEM SET max_parallel_maintenance_workers = '4'\" && yarn local:postgres:psql -c \"ALTER SYSTEM SET effective_io_concurrency = '200'\" || echo '\n(no need to set effective_io_concurrency on macOS, tuning complete. 👍)'",