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
As pointed out by Stefan Marr inline caches could help improve lookup performance in the current JIT and even the interpreter. This is probably the simplest thing we can do right now to improve send performance (I wouldn't expect too much of a speedup though).
We might be able to add the cache to a CompiledMethod object on the fly. It could be a dictionary indexed by the send's pc.
Something would need to be stored in the selector objects too, for invalidation. Maybe a list of dict+pc pairs so individual entries can be invalidated.
Might need to hook into finalization to clean out garbage in these.
As pointed out by Stefan Marr inline caches could help improve lookup performance in the current JIT and even the interpreter. This is probably the simplest thing we can do right now to improve send performance (I wouldn't expect too much of a speedup though).
We might be able to add the cache to a
CompiledMethod
object on the fly. It could be a dictionary indexed by the send'spc
.Something would need to be stored in the selector objects too, for invalidation. Maybe a list of dict+pc pairs so individual entries can be invalidated.
Might need to hook into finalization to clean out garbage in these.
Ref: https://www.complang.tuwien.ac.at/kps09/pdfs/brunthaler.pdf
The text was updated successfully, but these errors were encountered: