Difference between revisions of "Blockfrost-ryo"
Jump to navigation
Jump to search
↑ https://github.com/blockfrost/blockfrost-backend-ryo/releases/tag/v1.0.0
(11 intermediate revisions by the same user not shown) | |||
Line 11: | Line 11: | ||
blockfrost/backend-ryo:latest | blockfrost/backend-ryo:latest | ||
+ | |||
+ | |||
+ | System requirements | ||
+ | The system requirements for the basic Blockfrost backend stack (which means <code>[[blockfrost-backend]], [[cardano-node]], [[cardano-db-sync]]</code> and <code>[[postgresql]]</code> on the same machine) are: | ||
+ | * 64 GB of RAM or more | ||
+ | * 8 CPU cores or more | ||
+ | * 250 GB of disk space or more | ||
+ | * SSD disk with at least 80k IOPS (measured as chunk size) | ||
* Releases: https://github.com/blockfrost/blockfrost-backend-ryo/releases | * Releases: https://github.com/blockfrost/blockfrost-backend-ryo/releases | ||
** [[CIP68]] | ** [[CIP68]] | ||
+ | ** Support for configurable memory settings for [[pm2]] in the [[nix]] service | ||
+ | |||
+ | == Optimization == | ||
+ | [[CREATE INDEX]] IF NOT EXISTS bf_idx_block_hash_encoded ON block USING HASH (encode(hash, 'hex')); | ||
+ | CREATE INDEX IF NOT EXISTS bf_idx_datum_hash ON datum USING HASH (encode(hash, 'hex')); | ||
+ | CREATE INDEX IF NOT EXISTS bf_idx_multi_asset_policy ON multi_asset USING HASH (encode(policy, 'hex')); | ||
+ | CREATE INDEX IF NOT EXISTS bf_idx_multi_asset_policy_name ON multi_asset USING HASH ((encode(policy, 'hex') || encode(name, 'hex'))); | ||
+ | CREATE INDEX IF NOT EXISTS bf_idx_pool_hash_view ON pool_hash USING HASH (view); | ||
+ | CREATE INDEX IF NOT EXISTS bf_idx_redeemer_data_hash ON redeemer_data USING HASH (encode(hash, 'hex')); | ||
+ | CREATE INDEX IF NOT EXISTS bf_idx_scripts_hash ON script USING HASH (encode(hash, 'hex')); | ||
+ | CREATE INDEX IF NOT EXISTS bf_idx_tx_hash ON tx USING HASH (encode(hash, 'hex')); | ||
+ | [[CREATE UNIQUE INDEX]] IF NOT EXISTS bf_u_idx_epoch_stake_epoch_and_id ON epoch_stake (epoch_no, id); | ||
+ | CREATE INDEX IF NOT EXISTS bf_idx_reference_tx_in_tx_in_id ON reference_tx_in (tx_in_id); | ||
+ | CREATE INDEX IF NOT EXISTS bf_idx_collateral_tx_in_tx_in_id ON collateral_tx_in (tx_in_id); | ||
+ | |||
+ | == Related == | ||
+ | * [[Blockfrost logs|Errors]] | ||
+ | * [[cardano-db-sync]] | ||
== See also == | == See also == | ||
+ | * {{blockfrost-ryo}} | ||
* {{Blockfrost}} | * {{Blockfrost}} | ||
[[Category:Cardano]] | [[Category:Cardano]] |
Latest revision as of 07:39, 9 May 2023
(Sep 2022) [1]
docker run --rm \ --name blockfrost-ryo \ -p 3000:3000 \ -e BLOCKFROST_CONFIG_SERVER_LISTEN_ADDRESS=0.0.0.0 \ -v $PWD/config:/app/config \ blockfrost/backend-ryo:latest
System requirements
The system requirements for the basic Blockfrost backend stack (which means blockfrost-backend, cardano-node, cardano-db-sync
and postgresql
on the same machine) are:
- 64 GB of RAM or more
- 8 CPU cores or more
- 250 GB of disk space or more
- SSD disk with at least 80k IOPS (measured as chunk size)
Optimization[edit]
CREATE INDEX IF NOT EXISTS bf_idx_block_hash_encoded ON block USING HASH (encode(hash, 'hex')); CREATE INDEX IF NOT EXISTS bf_idx_datum_hash ON datum USING HASH (encode(hash, 'hex')); CREATE INDEX IF NOT EXISTS bf_idx_multi_asset_policy ON multi_asset USING HASH (encode(policy, 'hex')); CREATE INDEX IF NOT EXISTS bf_idx_multi_asset_policy_name ON multi_asset USING HASH ((encode(policy, 'hex') || encode(name, 'hex'))); CREATE INDEX IF NOT EXISTS bf_idx_pool_hash_view ON pool_hash USING HASH (view); CREATE INDEX IF NOT EXISTS bf_idx_redeemer_data_hash ON redeemer_data USING HASH (encode(hash, 'hex')); CREATE INDEX IF NOT EXISTS bf_idx_scripts_hash ON script USING HASH (encode(hash, 'hex')); CREATE INDEX IF NOT EXISTS bf_idx_tx_hash ON tx USING HASH (encode(hash, 'hex')); CREATE UNIQUE INDEX IF NOT EXISTS bf_u_idx_epoch_stake_epoch_and_id ON epoch_stake (epoch_no, id); CREATE INDEX IF NOT EXISTS bf_idx_reference_tx_in_tx_in_id ON reference_tx_in (tx_in_id); CREATE INDEX IF NOT EXISTS bf_idx_collateral_tx_in_tx_in_id ON collateral_tx_in (tx_in_id);
Related[edit]
See also[edit]
Advertising: