Self hosted fullnode migrate from JSON-RPC to gRPC

General
1

I run a self-hosted SUI fullnode and plan to migrate from JSON-RPC to gRPC or GraphQL RPC.
When I enable gRPC indexing, got logs below, then

Jul 10 02:18:38 sui01-stg sui-node[1210176]: 2026-07-10T02:18:38.503234Z WARN live_object_set_index_task{task_id=5 bits=5}: typed_store::rocks: very slow batch write elapsed=12.626709761 db_name=“rpc-index”

fullnode sui version: testnet-v1.75.1

my testnet hardware sepc is
cpu 8 cores
disc space 2TB (not NVMe)
32GB ram
ubuntu

Or, if I use GraphQL RPC, should still need to enable gRPC indexing?

please help me, thanks.

2

Hi there!

The slow indexing times you are running into are tied to your hardware. Your current setup falls a bit below the recommended specifications, which is causing the bottleneck.

here are the recommended specs for a Sui fullnode (ref):

  • CPU: 8 physical cores / 16 vCPUs

  • RAM: 128 GB

  • Storage: 4 TB NVMe drive

Given your current hardware, you might want to evaluate how you plan to use this node so you can optimize your setup:

  • Full API Setup: If you need the complete fullnode API (like gRPC), you will likely need to upgrade your hardware to handle the heavy indexing load

  • Self-Serving (GraphQL): If this node is just for your own use, you can skip the heavy indexing on the node itself. Instead, you can run the GraphQL stack as a completely separate service. You would set up its own indexer pipelines and a PostgreSQL database (using the sui-indexer-alt-graphql service). In this setup, your fullnode isn’t the data source at all — it just acts as a backend for executing transactions.

1 Like