You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
cd gnovm/stdlibs/bytes
gno test -v -run=TestCompareIdentical .
=== RUN TestCompareIdenticalSlice
--- PASS: TestCompareIdenticalSlice (0.00s)
ok . 76.10s
76.10 seconds to run a single test is too long and that impedes the speed of development
For a comparison, the equivalent in the Go standard library takes less than 1 second
$ go test -run=CompareIdentical -v
=== RUN TestCompareIdenticalSlice
--- PASS: TestCompareIdenticalSlice (0.00s)
PASS
ok bytes 0.048s
and to run even the entire suite of tests in the Go bytes packages takes less than 1 second
PASS
ok bytes 0.974s
Your environment
Go version:go version devel go1.24-6405e60ca6 Wed Nov 27 06:35:34 2024 +0000 linux/amd64
OS and CPU architecture: linux/amd64
Gno commit hash causing the issue (example: f24690e)
Suggestion
I highly recommend that performance of such be looked at as a serious incentive to make performance a huge win for not only tests and velocity of improvements but also for general performance.If the tests take 70X longer than the standard library, then even the VM must be suffering with bad performance and has been undiagnosed for a while.
The text was updated successfully, but these errors were encountered:
Description
If I do
76.10 seconds to run a single test is too long and that impedes the speed of development
For a comparison, the equivalent in the Go standard library takes less than 1 second
$ go test -run=CompareIdentical -v === RUN TestCompareIdenticalSlice --- PASS: TestCompareIdenticalSlice (0.00s) PASS ok bytes 0.048s
and to run even the entire suite of tests in the Go bytes packages takes less than 1 second
Your environment
Suggestion
I highly recommend that performance of such be looked at as a serious incentive to make performance a huge win for not only tests and velocity of improvements but also for general performance.If the tests take 70X longer than the standard library, then even the VM must be suffering with bad performance and has been undiagnosed for a while.
The text was updated successfully, but these errors were encountered: