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
I'm not 100% sure, but I think RandomXVM could also implement the Send trait. There doesn't seem anything that would make dropping a VM in a different thread unsound. It would allow putting it in a ThreadLocal to avoid recreating VMs every time a proof of work needs to be calculated. It would be useful for scenarios where many pows need to be verified in a short time.
Note: these traits are implemented by the archived moneromint/randomx4r:
Currently, neither
RandomXCache
,RandomXDataset
norRandomXVM
implementSend
andSync
.I think cache and dataset could implement both
Send
andSync
. For example, these structures are shared by VMs working in different threads in RandomX benchmarks: https://github.com/tevador/RandomX/blob/040f4500a6e79d54d84a668013a94507045e786f/src/tests/benchmark.cpp#L340-L365. It is essential to reuse cache and dataset to achieve high hashing rate using multiple threads.I'm not 100% sure, but I think
RandomXVM
could also implement theSend
trait. There doesn't seem anything that would make dropping a VM in a different thread unsound. It would allow putting it in a ThreadLocal to avoid recreating VMs every time a proof of work needs to be calculated. It would be useful for scenarios where many pows need to be verified in a short time.Note: these traits are implemented by the archived moneromint/randomx4r:
What do you think?
The text was updated successfully, but these errors were encountered: