BUG: Block production is taking long time.

[vatsa287]

2024-12-11 09:04:04 💤 Idle (2 peers), best: #1626 (0x01c8…a1ab), finalized #1624 (0x231b…1d99), ⬇ 1.5MiB/s ⬆ 1.5MiB/s    
2024-12-11 09:04:05 🆕 Imported #1626 (0xd597…3bdf → 0x9752…d325)    
2024-12-11 09:04:05 🙌 Starting consensus session on top of parent 0x01c809e35083eef8e1b1e65b11b9b1e89eecfc43e48b49905427e0181442a1ab    

2024-12-11 09:04:07 ⌛️ Discarding proposal for slot 577969281; block production took too long    

2024-12-11 09:04:08 🎁 Prepared block for proposing at 1627 (2742 ms) [hash: 0x3baaf9747f1b4545dde4cd5a03465ab01c4970ab3f06ba4d28bdf5f109a85087; parent_hash: 0x01c8…a1ab; extrinsics (3): [0xbb95…d7d4, 0xaeeb…3e7d, 0x4792…de76]    
2024-12-11 09:04:08 🏆 Imported #1627 (0x01c8…a1ab → 0x077a…4f31)    
2024-12-11 09:04:09 🙌 Starting consensus session on top of parent 0x077a5099b0c0d9ff78245225b9db2e9352b708f188caaffee7809eee4a1e4f31    
2024-12-11 09:04:09 💤 Idle (2 peers), best: #1627 (0x077a…4f31), finalized #1624 (0x231b…1d99), ⬇ 751.7kiB/s ⬆ 1.5MiB/s    
2024-12-11 09:04:11 🎁 Prepared block for proposing at 1628 (2691 ms) [hash: 0x212ca0a0ac47b0d85b2cc1835280d03b419355d0e1ef8742aa9c7183f2403200; parent_hash: 0x077a…4f31; extrinsics (3): [0x076c…b504, 0x6fa9…00ad, 0x2632…7406]    

One of logs on weave.testnet.cord.network where the benchmarking based on dedi pallets are taking place are sending out these statement periodically.

What causes this and does this hamper the getting the transaction finalised?

^ @smohan-dw @amarts

[amarts]

block production took too long is generally happens because of weights mismatch?

Ie, the logic of weights helps to make sure all computation (for 'every' validators in chain) are completed within the time, so they can vote on it.