Store stats per entry, not per function #192
Description
Is your feature request related to a problem?
Storing stats (e.g. time to compute) per function might be too coarse. For example, the time to compute might vastly differ based on the inputs.
Desired solution
Create benchmarks to determine whether storing the stats per entry is better.
At first glance, entry stats are great to determine which values to remove from the memo table, and functions stats are great to check whether memoizing a value is worth it at all.
Possible alternatives (optional)
No response
Screenshots (optional)
No response
Additional Context (optional)
No response