neo-go/pkg/util/bench_test.go

package util

import (
	"testing"
)

func BenchmarkUint256MarshalJSON(b *testing.B) {
	v := Uint256{0x01, 0x02, 0x03}

	for range b.N {
		_, _ = v.MarshalJSON()
	}
}
util: optimize MarshalJSON allocations name old time/op new time/op delta Uint256MarshalJSON-8 230ns ± 6% 83ns ±13% -63.78% (p=0.000 n=8+10) name old alloc/op new alloc/op delta Uint256MarshalJSON-8 320B ± 0% 80B ± 0% -75.00% (p=0.000 n=10+10) name old allocs/op new allocs/op delta Uint256MarshalJSON-8 5.00 ± 0% 1.00 ± 0% -80.00% (p=0.000 n=10+10) 2022-06-01 08:26:36 +00:00			`package util`

			`import (`
			`"testing"`
			`)`

			`func BenchmarkUint256MarshalJSON(b *testing.B) {`
			`v := Uint256{0x01, 0x02, 0x03}`

*: improve for loop syntax Mostly it's about Go 1.22+ syntax with ranging over integers, but it also prefers ranging over slices where possible (it makes code a little better to read). Notice that we have a number of dangerous loops where slices are mutated during loop execution, many of these can't be converted since we need proper length evalutation at every iteration. Signed-off-by: Roman Khimov <roman@nspcc.ru> 2024-08-30 18:41:02 +00:00			`for range b.N {`
util: optimize MarshalJSON allocations name old time/op new time/op delta Uint256MarshalJSON-8 230ns ± 6% 83ns ±13% -63.78% (p=0.000 n=8+10) name old alloc/op new alloc/op delta Uint256MarshalJSON-8 320B ± 0% 80B ± 0% -75.00% (p=0.000 n=10+10) name old allocs/op new allocs/op delta Uint256MarshalJSON-8 5.00 ± 0% 1.00 ± 0% -80.00% (p=0.000 n=10+10) 2022-06-01 08:26:36 +00:00			`_, _ = v.MarshalJSON()`
			`}`
			`}`