Injective Mainnet node sync is unstable and slow

[arjunbhut]

Hello Everyone,

I’ve been running an Injective RPC node that was always in sync until recently. Over the past few days, the node has started to lag behind significantly and takes much longer to catch up. My hardware specifications are more than sufficient:

RAM: 128 GB
CPU: 12 cores
Storage: 3TB NVMe

I’m running the enterprise edition of NVMe drives and have confirmed that disk health is fine.

I’ve attached a graph that shows the node’s performance over time—it was consistently in sync before, but the lag has become noticeable now.

Does anyone know what might be causing this sudden delay? Are there any known issues or configuration changes that could be contributing to the problem, and what steps might help resolve it?

I also have around 35 peers and also tried updating the addrbook from polkachu and also tried letting pex auto discover the peers but still lag is persistent.

Below is the graph and my system usage which might help in debugging.

Thanks in advance for your insights.

[xinzhongyoumeng]

大家好，

我一直在运行一个 Injective RPC 节点，直到最近它一直保持同步。在过去的几天里，该节点开始明显落后，需要很长时间才能赶上。我的硬件配置完全够用：

RAM：128 GB CPU：12 核 存储：3TB NVMe

我正在运行 NVMe 驱动器的企业版，并已确认磁盘健康状况良好。

我附上了一张显示节点随时间变化的性能的图表——它之前始终保持同步，但现在滞后变得明显。

有人知道是什么原因导致了这种突然的延迟吗？是否存在任何已知问题或配置更改可能导致此问题？哪些步骤可能有助于解决此问题？

我也有大约 35 个对等点，也尝试从 polkachu 更新 addrbook，也尝试让 pex 自动发现对等点，但仍然存在滞后。

下面是图表和我的系统使用情况，可能有助于调试。

提前感谢您的见解。

Is there any progress?