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
Describe the bug GetProvisioners call consumes more than 4s (up to 15s on low-spec nodes) allegedly due to serialization in VM. Although this is not supposed to be the case with the optimized VM (next version), this should be handled gracefully from client-side (Golang part).
To Reproduce
Introduce 2000-size allow list
Call Accept/Finalize (as a result this calls GetProvisioners).
Expected behaviour
Until next VM is benchmark-ed and fully integrated, dusk node should not call grpc.GetProvisioners if provisioners list is not updated.
The text was updated successfully, but these errors were encountered:
Describe the bug
GetProvisioners
call consumes more than 4s (up to 15s on low-spec nodes) allegedly due to serialization in VM. Although this is not supposed to be the case with the optimized VM (next version), this should be handled gracefully from client-side (Golang part).To Reproduce
Expected behaviour
Until next VM is benchmark-ed and fully integrated, dusk node should not call
grpc.GetProvisioners
if provisioners list is not updated.The text was updated successfully, but these errors were encountered: