-
-
Notifications
You must be signed in to change notification settings - Fork 416
feat: use different snappy implementations for different topics #8670
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: cayman/snappy
Are you sure you want to change the base?
Conversation
Summary of ChangesHello @twoeths, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request introduces a strategic change to the Snappy decompression mechanism within the beacon node to resolve a performance bottleneck identified on SAS nodes. By selectively applying Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request introduces snappyjs for decompressing beacon_attestation messages to address performance regressions on certain nodes, while snappy-wasm is retained for other message types and all compression tasks. The changes are well-structured, using a decompressor interface and a factory function for selecting the appropriate implementation. My review focuses on improving the consistency and error handling between the two snappy implementations to make the new abstraction more robust.
| */ | ||
| export function getSnappyDecompressor(topicType: GossipType, data: Uint8Array): ISnappyDecompressor { | ||
| switch (topicType) { | ||
| case GossipType.beacon_attestation: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
also aggregate and proof?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I switched to use snappy-wasm for data_column_sidecar and beacon_block
for others use snappy-js
| @@ -0,0 +1,56 @@ | |||
| import {SnappyCompressor} from "./compressor.js"; | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice, this is snappyjs but converted to typescript?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should leave a comment here linking back to the upstream,
eg, // Based on snappyjs - https://github.com/zhipeng-jia/snappyjs
| return -1; | ||
| } | ||
|
|
||
| uncompressInto(outBuffer: Uint8Array): boolean { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
and we are now using this, which was previously hidden by our incomplete manually-crafted types
wemeetagain
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you update the snappy benchmarks with this impl of snappyjs?

Motivation
Description
Buffer.allocUnsafe()therebeacon_attestationtopic type andsnappy-wasmfor other topicsfeat3