-
Notifications
You must be signed in to change notification settings - Fork 173
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
Document that casm = true
in Scarb.toml slows the compilation
#2472
Comments
I am applying to this issue via OnlyDust platform. My background and how it can be leveragedHello I'm a front-end and a blockchain developer and will love to work on this |
I am applying to this issue via OnlyDust platform. My background and how it can be leveragedAm a technical writer How I plan on tackling this issuekindly assign ETA <= 78hrs |
I am applying to this issue via OnlyDust platform. My background and how it can be leveragedhello @ i'm an experienced frontend developer and a blockchain developer i would love to work on this issue |
I am applying to this issue via OnlyDust platform. My background and how it can be leveragedHi, I am ICT student and for the last few months i was really intrested in Rust and Cario. I also work professionallyas software developer. I hope can help you solve this and start my journey in Cario world How I plan on tackling this issueI’d locate Sierra compilation in snforge and sncast, address the USC and CASM overhead, and review version 0.23.0 changelogs for changes. |
I am applying to this issue via OnlyDust platform. My background and how it can be leveragedI have a solid background in software development, focusing on blockchain and toolchain optimization. My experience with various compilers, including StarkNet tools, allows me to manage complex build processes effectively. Additionally, my ability to write clear documentation will support updating the changelog and guiding users. How I plan on tackling this issueI will analyze how snforge and sncast compile programs to identify delays in large Sierra compilations. I will find ways to improve memory usage, streamline the USC process, and add caching to reduce slowdowns. I will update the documentation and changelog for clear user instructions. Finally, I will thoroughly test the changes for efficiency in both small and large Sierra programs. |
I am applying to this issue via OnlyDust platform. My background and how it can be leveragedHello, can I be assigned to work on this issue? I'm a software developer with over 4 years experience Here's my OnlyDust profile https://app.onlydust.com/u/raizo07 ETA: One day |
@NueloSE any progress on this? |
<!-- Reference any GitHub issues resolved by this PR --> Closes #2472 ## Introduced changes Add a description about the slow compilation when casm = true in scarb.toml file - ## Checklist - [x] Linked relevant issue - [x] Updated relevant documentation - [x] Added relevant tests - [x] Performed self-review of the code - [x] Added changes to `CHANGELOG.md` --------- Co-authored-by: Artur Michałek <[email protected]>
Which components does the task require to be changed? (think hard pls)
snforge, sncast
Description
We compile every sierra with USC anyways since Scarb gives no guarantee about CASM by design.
The overhead generated by this can be huge for big sierra programs (couple dozens of MB). It was only mentioned changelog of 0.23.0 version. It should be done in this file here
The text was updated successfully, but these errors were encountered: