Significantly long GnoVM test runtime about gno HOT 4 OPEN

Maybe we should make the VM thread-safe, to make it possible to run several of them simultaneously.

from gno.

to make it possible to run several of them simultaneously.

This is actually something that is required down the line, we can't do gas estimations (through an RPC call, cc @MichaelFrazzy) and state transitions at the same time with the current VM

from gno.

Maybe we should make the VM thread-safe, to make it possible to run several of them simultaneously.

I also lean towards this idea.
I made a profile on the slowest tests and the distribution of runtime is kind of equal across the board.
In other words, there is no single function bottleneck.
The only one that takes more than 2% of the runtime is

// NOTE: for allocation, use *Allocator.NewBlock.
func NewBlock(source BlockNode, parent *Block) *Block

It takes about 7% of the runtime.
It is worth improving it. It wouldn't fix the tests runtime, we still need to make them thread safe but it will help a bit with that and also make the general runtime faster.

from gno.

to make it possible to run several of them simultaneously.

This is actually something that is required down the line, we can't do gas estimations (through an RPC call, cc @MichaelFrazzy) and state transitions at the same time with the current VM

Is this test similar in function to the benchmarking framework that Dylan set up or something that we've had for a while?

from gno.