Optimization records

Question

Optimization records

Opened this issue a year ago · 3 comments

lhmouse commented a year ago

Some obvious issues:

1. Memory allocation of stacks and contexts also costs very much, but it can be mitigated by linking against tcmalloc.
2. The cost of construction (17.28%) and destruction (10.52%) of an Executive_Context for a function call is too high.
3. There are too many (2.5x plain calculation) name lookups for local variables, and the cost (18.00%) is non-negligible.

Answer 1 · 2023-11-16T09:49:23.000Z

lhmouse commented a year ago

Answer 2 · 2023-11-25T12:48:48.000Z

lhmouse commented a year ago

Answer 3 · 2023-12-03T14:43:27.000Z

Looks like we can save ~10% by making all reference counts non-atomic. Replacing all of them is of course impractical, but can we replace some of them?