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
SputnikVM is running based on per-transaction, it means, starting 'sputnikVM' for every transaction by accepting transaction, header parameter and freeing at end of execution of transaction. It would require some resources (time) to do all these. It might affect the performance of the nodes.
Instead of above approach, can we have the feature of initiating the sputnikVM while starting the node using the same instance to execute the transactions which will save a lots of time.
As you can see in the implementation of EVM by microsoft They are creating an instance and using the same instance to run the transactions.
This feature will helps us to read config at start up. Look at #370
The text was updated successfully, but these errors were encountered:
SputnikVM is running based on per-transaction, it means, starting 'sputnikVM' for every transaction by accepting transaction, header parameter and freeing at end of execution of transaction. It would require some resources (time) to do all these. It might affect the performance of the nodes.
Instead of above approach, can we have the feature of initiating the sputnikVM while starting the node using the same instance to execute the transactions which will save a lots of time.
As you can see in the implementation of EVM by microsoft They are creating an instance and using the same instance to run the transactions.
This feature will helps us to read config at start up. Look at #370
The text was updated successfully, but these errors were encountered: