ssv reconstruct randao task sometimes very slow

[hwhe]

Describe the bug
The ssv proposal a block as follows:

1. sign a partial randao sig and wait for 2f+1 partial sigs from peers
2. reconstruct randao and send GetBeaconBlock to BN
3. start consensus on duty + block data
4. Once consensus decides, sign partial block and broadcast
5. collect 2f+1 partial sigs, reconstruct and broadcast valid block sig to the BN

My four ssv operators are running on four ECSs and in the same geographical location.
The time difference is large if only the time required for the first step is analyzed. Sometimes it's 100ms, sometimes it's 1200ms.

I'd like to know what factors affect the time taken for the first step?
What can I do so that the four operators can quickly complete the reconstruct randao task?

Expected behavior
Do reconstruct randao work quickly, don't drag out the block the whole time.

Screenshots
If applicable, add screenshots to help explain your problem.

Node (please complete the following information):

• Operator Version: [v1.3.2]
• BN Client [Lighthouse v5.1.3]

Additional context
key logs:
38:47.003671Z ℹ️ starting duty processing {"pubkey": "", "role": "PROPOSER", "slot": , "role": "PROPOSER", "duty_id": "", "height": 0}
38:49.472355Z 🧊 got beacon block proposal {"pubkey": "", "role": "PROPOSER", "duty_id": "", "slot": , "block_hash": "", "blinded": true, "took": "1.222895737s"}
38:52.961854Z ✅ successfully submitted block proposal {"pubkey": "", "role": "PROPOSER", "duty_id": "*", "slot": *, "height": *, "round": 1, "block_hash": "0x0000000000000000000000000000000000000000000000000000000000000000", "blinded": false, "took": "2.660469486s"}

49.472355Z - 1.222895737s = 48.249459263
We can see that sign a partial randao sig and reconstruct randao task took 1200 milliseconds, very slow.

[y0sher]

Hi @hwhe , I'm very sorry on the delay, all the team is busy with a very big feature we're introducing soon. If github issues are left un answered, shooting us a discord message might speed it up.

The time for the "first step" - when you see got beacon block proposal is the time it takes to get the block from your beacon node, it seems that you're having some delay there, 1.2s is pretty slow, many things might cause this but without more info into your setup we won't be able to help.
from my experience it might be -

• beacon node low resources
• 4 ssv nodes using same beacon node (especially if last point is also true) or other services using the beacon node