Closed zhy827827 closed 23 hours ago
Thank you for reporting this @zhy827827 ! This is a known issue and the source cause is the same as in https://github.com/paritytech/substrate-api-sidecar/issues/1554. The problem occurs when the queried blocks contain an unusually high volume of extrinsics. We are currently evaluating different approaches to address this performance bottleneck and we will update you once we have concrete next steps and action items. Thank you for your patience.
@zhy827827
Please expect a possible decline in Sidecar performance starting at approximately 14:00 UTC today and lasting for around 40 minutes. This is due to an expected Spammening event on the Polkadot network.
During this period, Sidecar endpoints like blocks
, staking-info
and others may be affected, as we expect a high volume of 2.000-5.000 transactions per block.
To mitigate the potential performance impact, we recommend the following:
--max-old-space-size
flag in your process startup command.noFees=true
and finalizedKey=false
flags for the blocks
endpoint to reduce the data payload.Related docs: Showcasing Polkadot’s Capabilities: The Spammening
@Imod7 thank you very much
version: parity/polkadot:stable2409-2 parity/substrate-api-sidecar:v19.3.1
Sidecar logs: