feat: update retry mechanism

[greged93]

closes: #319

[codspeed-hq]

CodSpeed Performance Report

Merging #358 will improve performances by 34.14%

_{Comparing feat/update-retry (1b7b64f) with main (243b212)}

Summary

⚡ 1 improvement
✅ 1 untouched

Benchmarks breakdown

	Benchmark	BASE	HEAD	Change
⚡	pipeline_derive_in_file_blobs	968.5 ms	722 ms	+34.14%

[frisitano]

Looks great! Added some minor comments inline, primiarly about when we should use the raw methods and when to instantiate a transaction.

[frisitano]

lgtm

[greged93]

@frisitano should we merge this with the old benchmark and fix in another PR?

[frisitano]

@frisitano should we merge this with the old benchmark and fix in another PR?

Yes lets revent back to the old bencmarks, get CI green and merge. We can look at codespeed in another PR as you suggest.

[greged93]

@frisitano regression seems to have came from not having a get_n_block_data_hint. With the added method in 22e5d4c, regression is corrected.

[frisitano]

@frisitano regression seems to have came from not having a get_n_block_data_hint. With the added method in 22e5d4c, regression is corrected.

Can you elaborate on this please? In main we don't have a get_n_block_data_hint so why would this result in a regression?

Also looks like CI isn't passing

edit: Is this because in the derivation pipeline using the new api we would create a new transaction for each block data hint we fetched?

[frisitano]

Looks good. lgtm

[greged93]

edit: Is this because in the derivation pipeline using the new api we would create a new transaction for each block data hint we fetched?

Yes, it seems like this slows the derivation process.

[frisitano]

lgtm