-
Notifications
You must be signed in to change notification settings - Fork 27
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
Improve Zero-Copy Compliance: LifeTimes Parameters, Arrays Usage, and String Alternatives (Priority on Sana) #464
Comments
I am applying to this issue via OnlyDust platform. My background and how it can be leveragedWith over four years in blockchain and backend development, I’ve worked across different ecosystems, handling everything from smart contract design to on-chain interactions and protocol integration. I focus on building secure, scalable, and reliable blockchain applications, managing both on-chain and off-chain infrastructure. How I plan on tackling this issueI'd start by reviewing the sana crate, and identifying areas in which these optimizations can be done. So first job would be to outline the possible optimizations while adhering to the zero copy principles. After the outline with feedback from team would proceed to effect the changes. |
I am applying to this issue via OnlyDust platform. My background and how it can be leveragedI have experience in Rust: and I've do some optimization here: near/near-sdk-rs#746 How I plan on tackling this issueAs mentioned in the issue, there are some points to improve to gradually achieve zero-copy:
I will implement changes incrementally and make sure to write and conduct comprehensive tests, and figure out the way to benchmark the effectiveness of the refactor. |
I am applying to this issue via OnlyDust platform. My background and how it can be leveragedI have experience in Rust and memory optimization techniques like Zero-Copy. I’ve worked with Lifetimes, array management, and buffer structures to improve performance and reduce memory overhead in systems. How I plan on tackling this issueI’d first review the Sana module and identify areas where Lifetimes and array usage can be optimized. I’d explore using circular buffers as alternatives to strings, ensuring compliance with Zero-Copy principles. I’d also test for performance improvements and memory efficiency. |
I am applying to this issue via OnlyDust platform. My background and how it can be leveragedI have experience with memory optimization and performance-critical systems in Rust and TypeScript, focusing on zero-copy principles, lifetimes, and data structures like circular buffers. My work includes optimizing array usage, reducing memory overhead, and ensuring safe memory management, which will directly apply to improving Zero-Copy compliance in the Ark Project's Sana module. How I plan on tackling this issueI’d optimize lifetimes to reduce unnecessary copying, improve memory safety, streamline array usage by minimizing allocations with slices or fixed-size arrays, replace strings with circular buffers to reduce heap allocations, and ensure minimal data copying across functions and modules. |
I am applying to this issue via OnlyDust platform. My background and how it can be leveragedi am a full time blockchain engineer working on a vm running in rollup in rust
How I plan on tackling this issue
I will make sure i add changes incrementally and use memory profiling. |
Hi @ybensacq , can I get this done please? I’m ready to work. |
We need to review and improve the Zero-Copy compliance in the Ark Project, with a focus on the Sana module.
Some areas where improvements are needed include:
Addressing these areas will help to optimize memory usage and improve the overall efficiency of the project. Contributions and suggestions are highly appreciated, especially on Sana, as it is our priority at the moment.
Looking forward to your input!
The text was updated successfully, but these errors were encountered: