Skip to content

update Database configuration #558

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Benson0224 merged 2 commits into from
Apr 17, 2026
Merged

update Database configuration #558

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5b6829f
Update Hardware Configuration Requirements related
GordonLtron Mar 18, 2026
947d9e9
update :Database Configuration
GordonLtron Mar 18, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/architecture/database.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,11 +5,11 @@ In the TRON Java implementation (**java-tron**), the node data storage engine of
Database support varies by architecture:

- On x86_64 architecture, both LevelDB and RocksDB are supported, and the current version of RocksDB is v5.15.10.
- On arm64 architecture, only RocksDB is supported, and the current version of RocksDB is v9.7.4.
- On arm64 architecture, only RocksDB is supported, and the current RocksDB version is v9.7.4.

Developers can flexibly choose the appropriate storage engine based on the platform environment, hardware conditions, and performance requirements.
Developers can choose the appropriate storage engine based on the platform environment, hardware conditions, and performance requirements.

In comparison, **RocksDB provides richer configuration parameters and generally offers higher storage efficiency**. This article will introduce how to enable RocksDB and how to convert from LevelDB to RocksDB on x86_64 platforms.
In comparison, **RocksDB provides richer configuration parameters and generally offers higher storage efficiency**. This article introduces how to enable RocksDB and how to migrate from LevelDB to RocksDB on x86_64 platforms.

## Using RocksDB

Expand Down
10 changes: 6 additions & 4 deletions docs/using_javatron/installing_javatron.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

This document guides developers on how to deploy a TRON java-tron node on `Linux` or `macOS` operating systems.

Currently, a java-tron node supports running on both x86_64 and arm64 architectures(Support for the arm64 architecture starts from version 4.8.1). JDK support varies by architecture:
Currently, a java-tron node supports running on both x86_64 and arm64 architectures(support for the arm64 architecture starts from version 4.8.1). JDK support varies by architecture:

- On x86_64 architecture, currently only Oracle JDK 8 is supported.
- On arm64 architecture, currently only JDK 17 is supported.
Expand Down Expand Up @@ -188,7 +188,7 @@ nohup java -Xmx9G -XX:+UseZGC \
* `-XX:+UseZGC`: Enables ZGC, a scalable low-latency garbage collector.
* `-Xlog:gc...`: Unified JVM logging configuration. The example configures GC logs with file rotation (10 files, 100MB each).

### Staring a FullNode on the Nile test network
### Starting a FullNode on the Nile test network
Utilize the `-c` flag to direct the node to the configuration file corresponding to the desired network. Since Nile TestNet may incorporate features not yet available on the MainNet, it is **strongly advised** to compile the source code following the [Building the Source Code](https://github.com/tron-nile-testnet/nile-testnet/blob/master/README.md#building-the-source-code) instructions for the Nile TestNet.

```bash
Expand Down Expand Up @@ -355,8 +355,8 @@ To avoid specifying the private key in plaintext within the configuration file,

2. **Starting a Block Production Node**:

* **Starting the node interactively without `nohup` (Recommended)**
* **Important Notes**: This method requires human interaction to enter the password during node startup. It is recommended to use a session persistence tool, such as `screen` or `tmux`.
* **Interactive Startup without `nohup` (Recommended)**
* **Notes**: This method requires manually entering the password during node startup. It is highly recommended to run this inside a session persistence tool like screen or tmux."

```
java -Xmx24g -XX:+UseConcMarkSweepGC -jar build/libs/FullNode.jar --witness -c framework/src/main/resources/config.conf
Expand All @@ -373,6 +373,8 @@ To avoid specifying the private key in plaintext within the configuration file,
### Optimizing Memory Usage with `tcmalloc`

To achieve optimal memory usage, use Google's `tcmalloc` instead of the system's `glibc malloc`.
**Note**:
If you are deploying via the official java-tron Docker image (version 4.8.1 or later), `tcmalloc` is already integrated by default and no manual configuration is required.

1. **Install `tcmalloc`**:
* **Ubuntu 20.04 LTS / Ubuntu 18.04 LTS / Debian stable**:
Expand Down