GitBulletin

Repository: farcasterxyz/hub-monorepo

Revolutionary Performance Boost: Multi-Worker Strategy Unleashed!

2024-04-30 14:18:32 UTC

Hubble App Supercharges Message Validation with Cutting-Edge Optimization, Maximizing Efficiency Like Never Before!

Commit Details:

perf: Use all workers for validateOrRevokeMessages job (#1962) ## Motivation We were awaiting each message in validateOrRevokeMessagesJob even though we have multiple workers available. Fix ## Change Summary Describe the changes being made in 1-2 concise sentences. ## Merge Checklist _Choose all relevant options below by adding an `x` now or at any time before submitting for review_ - [X] PR title adheres to the [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/) standard - [X] PR has a [changeset](https://github.com/farcasterxyz/hub-monorepo/blob/main/CONTRIBUTING.md#35-adding-changesets) - [ ] PR has been tagged with a change label(s) (i.e. documentation, feature, bugfix, or chore) - [ ] PR includes [documentation](https://github.com/farcasterxyz/hub-monorepo/blob/main/CONTRIBUTING.md#32-writing-docs) if necessary. - [X] All [commits have been signed](https://github.com/farcasterxyz/hub-monorepo/blob/main/CONTRIBUTING.md#22-signing-commits) <!-- start pr-codex --> --- ## PR-Codex overview This PR focuses on improving performance by using multiple workers for the `validateOrRevokeMessages` job in the Hubble app. ### Detailed summary - Implemented the usage of multiple workers for the `validateOrRevokeMessages` job in the Hubble app for improved performance. - Updated function calls in various files to use the new `dbFetchIteratorPageByPrefix` method. - Replaced specific `statsd` initialization parameters with `ClientOptions` for better configuration handling. > The following files were skipped due to too many changes: `apps/hubble/src/storage/engine/index.ts`, `apps/hubble/src/storage/jobs/validateOrRevokeMessagesJob.ts`, `apps/hubble/src/storage/db/rocksdb.test.ts`, `apps/hubble/src/addon/src/db/rocksdb.rs` > ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}` <!-- end pr-codex -->

Search Similar