Skip to content
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.

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

Delay in First SOC Upload After Node Startup #4860

Open
nugaon opened this issue Oct 11, 2024 · 0 comments
Open

Delay in First SOC Upload After Node Startup #4860

nugaon opened this issue Oct 11, 2024 · 0 comments
Labels
needs-triaging new issues that need triaging

Comments

@nugaon
Copy link
Member

nugaon commented Oct 11, 2024

Context

  • Bee version: 2.2

Summary

After starting the node, the first Single Owner Chunk (SOC) upload takes an unusually long time. It appears that there might be a lock causing this delay, particularly around a specific debug log entry.

Expected behavior

The SOC upload should occur promptly after the node starts without significant delays.

Actual behavior

The first SOC upload after node startup is delayed significantly. The suspected cause is a lock around the following log entry:

"time"="2024-10-10 14:54:36.734229" "level"="debug" "logger"="node/salud" "msg"="computed" "avg_dur"=0.001058165 "pDur"=0.001001986 "pConns"=1 "network_radius"=0 "neighborhood_radius"=0 "batch_commitment"=191889408

Steps to reproduce

  1. Start the node with the usual configuration.
  2. Attempt to upload a SOC immediately after the node becomes operational.
  3. Observe the delay in the upload and check the node's log for the debug entry mentioned above.

Possible solution

Investigate the locking mechanism around the log entry point to determine if it is necessary or if it can be optimized to allow faster processing. This might involve reviewing the synchronization strategy around the shared resources involved in the SOC upload process.

@nugaon nugaon added the needs-triaging new issues that need triaging label Oct 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-triaging new issues that need triaging
Projects
None yet
Development

No branches or pull requests

1 participant