Solving issue of finalized meta after processed block #365
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
godmodegalactus
force-pushed
the
solving_issue_of_finalized_meta_after_processed_block
branch
from
1610681 to
96b082f
Compare
godmodegalactus
added a commit
that referenced
this pull request
Mar 22, 2024
* Use jemalloc * Solving issue of finalized meta after processed block (#365) * Solving issue of finalized meta after processed block * Fixing the broken test * Minor changes --------- Co-authored-by: Christian Kamm <[email protected]>
ckamm
added a commit
that referenced
this pull request
Mar 22, 2024
This reverts commit c09700f. Production runs show more stable memory use but worse performance on landing transactions.
grooviegermanikus
pushed a commit
that referenced
this pull request
Mar 22, 2024
* Use jemalloc * Solving issue of finalized meta after processed block (#365) * Solving issue of finalized meta after processed block * Fixing the broken test * Minor changes --------- Co-authored-by: Christian Kamm <[email protected]>
godmodegalactus
added a commit
that referenced
this pull request
Mar 25, 2024
* Use jemalloc * Solving issue of finalized meta after processed block (#365) * Solving issue of finalized meta after processed block * Fixing the broken test * Removing unwanted logs * Add logs on block queues and reception time * reduce level of block reception log * Revert "Solving issue of finalized meta after processed block (#365)" This reverts commit c09700f. Production runs show more stable memory use but worse performance on landing transactions. * use yellowstone grpc with hacked-windowsize * upgraded geyser-grpc-connector + increased timeout * Fix block stream throughput problems By temporarily pasting in a function to connect to block streams via a more generously configured endpoint. * Enabling unstable tokio on fly * update to v0.10.3+yellowstone.1.12+solana.1.17.15-hacked-windowsize3 --------- Co-authored-by: Christian Kamm <[email protected]> Co-authored-by: GroovieGermanikus <[email protected]>
godmodegalactus
added a commit
that referenced
this pull request
Mar 27, 2024
* Use jemalloc * Solving issue of finalized meta after processed block (#365) * Solving issue of finalized meta after processed block * Fixing the broken test * Removing unwanted logs * Add logs on block queues and reception time * reduce level of block reception log * Revert "Solving issue of finalized meta after processed block (#365)" This reverts commit c09700f. Production runs show more stable memory use but worse performance on landing transactions. * use yellowstone grpc with hacked-windowsize * upgraded geyser-grpc-connector + increased timeout * Fix block stream throughput problems By temporarily pasting in a function to connect to block streams via a more generously configured endpoint. * Enabling unstable tokio on fly * Fixing prioritization heap metrics (#370) * Fixing prioritization heap metrics * Fixing transaction sizes tests * Correctly ending the block streams instead of aborting them * Replacing exit signal with exit notification (#372) * Replacing exit signal with exit notification * Deprecitating nightly version * Increase connection size * Fixing issue with multiple notify channels * Joining heap task instead of aborting * fix postgres ssl algo issue - RC2-40-CBC (#373) * fix 373: openssl-legacy.cnf * Remove replace console subscriber with tracing subscriber --------- Co-authored-by: Christian Kamm <[email protected]> Co-authored-by: GroovieGermanikus <[email protected]> Co-authored-by: Groovie | Mango <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.