Open rsodre opened 3 weeks ago
just to add some quick context, i checked the memory usage on spawn-and-move example that is in the repo and memory usage was around 1.2GB for build and 3.5GB for running the test (it only has couple of tests).
and since sozo build and sozo test are light wrapper around scarb i dont think the issue is specially related to sozo, i will do a memory profile to confirm this.
origami token package: ~4GB during build, ~8.5GB during tests
sozo test --package origami_token
@rsodre please can I be assigned
For the record, scarb
has also notice significative increment of the compilation time. We may depend on what their bottleneck is.
@ShantelPeters do you have an idea of what could be dojo bottleneck related to compilation? Happy to assign if you have some suggestions.
Is there an scarb issue for that?
The language server is also consumes around 6GB.
Btw, running the same test with Dojo alpha 9, it's around 13GB
Describe the bug Running any simple tet on pistols consumes 18-20GB of RAM
To Reproduce
cd dojo
sozo test -f test_initialize_table
(any test will demonstrate there problem, this is a very simple one)sozo
and please notice this gas consumption on simple tests (test_initialize_table_defaults)...
Expected behaviour A clear and concise description of what you expected to happen.
Screenshots
Additional context
origami_token
package ERC-20 and ERC-721, and some openzeppelin utils.openzeppelin_test_common
to be able to run tests, even if not using any openzeppelin in the tests