ARCHIVE/rippled
1
0
Fork 0
mirror of https://github.com/XRPLF/rippled.git synced 2025-11-28 06:55:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

removed trailing whitespaces

Browse Source
This commit is contained in:
Valon Mamudi
2025-08-27 23:57:11 +02:00
parent 2f155d9273
commit b4eabf384e
1 changed files with 7 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
cfg/rippled-example.cfg
View File

@@ -979,19 +979,19 @@
# #
# nudb_block_size EXPERIMENTAL: Block size in bytes for NuDB storage. # nudb_block_size EXPERIMENTAL: Block size in bytes for NuDB storage.
# Must be a power of 2 between 4096 and 32768. Default is 4096. # Must be a power of 2 between 4096 and 32768. Default is 4096.
# #
# This parameter controls the fundamental storage unit # This parameter controls the fundamental storage unit
# size for NuDB's internal data structures. The choice # size for NuDB's internal data structures. The choice
# of block size can significantly impact performance # of block size can significantly impact performance
# depending on your storage hardware and filesystem: # depending on your storage hardware and filesystem:
# #
# - 4096 bytes: Optimal for most standard SSDs and # - 4096 bytes: Optimal for most standard SSDs and
# traditional filesystems (ext4, NTFS, HFS+). # traditional filesystems (ext4, NTFS, HFS+).
# Provides good balance of performance and storage # Provides good balance of performance and storage
# efficiency. Recommended for most deployments. # efficiency. Recommended for most deployments.
# Minimizes memory footprint and provides consistent # Minimizes memory footprint and provides consistent
# low-latency access patterns across diverse hardware. # low-latency access patterns across diverse hardware.
# #
# - 8192-16384 bytes: May improve performance on # - 8192-16384 bytes: May improve performance on
# high-end NVMe SSDs and copy-on-write filesystems # high-end NVMe SSDs and copy-on-write filesystems
# like ZFS or Btrfs that benefit from larger block # like ZFS or Btrfs that benefit from larger block
@@ -999,21 +999,21 @@
# databases. Offers better sequential throughput and # databases. Offers better sequential throughput and
# reduced I/O operations at the cost of higher memory # reduced I/O operations at the cost of higher memory
# usage per operation. # usage per operation.
# #
# - 32768 bytes (32K): Maximum supported block size # - 32768 bytes (32K): Maximum supported block size
# for high-performance scenarios with very fast # for high-performance scenarios with very fast
# storage. May increase memory usage and reduce # storage. May increase memory usage and reduce
# efficiency for smaller databases. Best suited for # efficiency for smaller databases. Best suited for
# enterprise environments with abundant RAM. # enterprise environments with abundant RAM.
# #
# Performance testing is recommended before deploying # Performance testing is recommended before deploying
# any non-default block size in production environments. # any non-default block size in production environments.
# #
# Note: This setting cannot be changed after database # Note: This setting cannot be changed after database
# creation without rebuilding the entire database. # creation without rebuilding the entire database.
# Choose carefully based on your hardware and expected # Choose carefully based on your hardware and expected
# database size. # database size.
# #
# Example: nudb_block_size=4096 # Example: nudb_block_size=4096
# #
# These keys modify the behavior of online_delete, and thus are only # These keys modify the behavior of online_delete, and thus are only