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
Allocating large objects (i.e. > 32 KiB) takes a while under Cannon. On my machine (AMD Ryzen 7 3700X), it takes about 7 seconds to allocate a 32 MB byte slice (i.e. execute a single runtime.makeslice call). It takes roughly the same amount of time for even larger allocations.
This doesn't seem to slow down op-program execution too much. Probably because it doesn't create too many large objects. However, we should improve this aspect of emulation to avoid future surprises.
The text was updated successfully, but these errors were encountered:
Inphi
changed the title
Improve emulation speed of Go allocation
Improve emulation speed of large object allocations in Go
Sep 11, 2024
Allocating large objects (i.e. > 32 KiB) takes a while under Cannon. On my machine (AMD Ryzen 7 3700X), it takes about 7 seconds to allocate a 32 MB byte slice (i.e. execute a single
runtime.makeslice
call). It takes roughly the same amount of time for even larger allocations.This doesn't seem to slow down op-program execution too much. Probably because it doesn't create too many large objects. However, we should improve this aspect of emulation to avoid future surprises.
The text was updated successfully, but these errors were encountered: