Skip to content

Conversation

@incrypto32
Copy link
Member

No description provided.

@incrypto32 incrypto32 force-pushed the krishna/cache-firehose-blocks branch 2 times, most recently from 84f8044 to d0fff45 Compare September 5, 2024 07:00
@incrypto32 incrypto32 changed the base branch from krishna/subgraph-comp-use-block-cache to krishna/switch-to-using-only-block-ptrs September 5, 2024 07:02
@incrypto32 incrypto32 force-pushed the krishna/cache-firehose-blocks branch 2 times, most recently from fed212a to 10c5c95 Compare September 5, 2024 08:07
@incrypto32 incrypto32 added this to the Subgraph Composition milestone Sep 10, 2024
@incrypto32 incrypto32 force-pushed the krishna/switch-to-using-only-block-ptrs branch from 856f3f4 to deaa413 Compare September 12, 2024 09:46
@incrypto32 incrypto32 force-pushed the krishna/cache-firehose-blocks branch from 10c5c95 to aed6de5 Compare September 12, 2024 09:48
@incrypto32 incrypto32 force-pushed the krishna/cache-firehose-blocks branch from aed6de5 to da218ec Compare October 7, 2024 08:31
@incrypto32 incrypto32 force-pushed the krishna/switch-to-using-only-block-ptrs branch from 4ad187b to e44444f Compare October 7, 2024 09:31
@incrypto32 incrypto32 force-pushed the krishna/cache-firehose-blocks branch from da218ec to 317ce7a Compare October 7, 2024 10:33
@incrypto32 incrypto32 marked this pull request as ready for review November 18, 2024 08:40
@incrypto32 incrypto32 requested a review from mangas November 18, 2024 08:40
@incrypto32 incrypto32 self-assigned this Nov 18, 2024

let start_time = Instant::now();

let result = chain_store
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isn't this the exact responsibility of the Block Ingestor? I also don't think this should be in here because there will always be 1 stream per subgraph so this would be amplifying any write attempts or any backoffs, on top of adding more time to processing. Caching blocks is already done on the ingestor, if we need more data that's where I think it should go or if we need a healing mechanism it seems like something different.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed, Im closing this PR as upon evaluating, this caching is no longer required since the use of cached block ptr's which is done in a later PR

@incrypto32 incrypto32 force-pushed the krishna/switch-to-using-only-block-ptrs branch 2 times, most recently from fae59fa to 4c0dc41 Compare November 19, 2024 11:23
@incrypto32 incrypto32 closed this Nov 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants