feat: use worker threads for CPU intensive message parsing #66
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
rafaelcr
approved these changes
Jan 9, 2025
zone117x
added a commit
that referenced
this pull request
Jan 9, 2025
* feat: ingest messages from redis * chore: rename chainhook related files * feat: ingest messages from redis * chore: move sql read/write type queries into correct classes * chore: disable postgres listen/notify usage for socket-io events * feat: use worker threads for CPU intensive message parsing (#66) * feat: use worker threads for CPU intensive message parsing * chore: misc fixes * fix: insert reward_sets for pre-naka blocks * chore: bump nodejs to v22 * ci: add `redis-stream` pre-release deployment
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
Offload CPU intensive msg parsing onto worker thread to prevent blocking main thread