Develop a generalized caching system for components #410
Description
Develop a generalized caching system for components
Some components have computationally expensive compute methods, such as HOPP or Floris.
We have some ad hoc solutions, but could probably benefit from a more generalized solution that can be coded once and used in multiple components.
Proposed solution
We could use an existing version of the caching within a PerformanceBaseClass, if you will.
Just like we have a cost base class, this might be the time to introduce a performance base class.
That's where we could house the generalized caching solution.
Alternatives considered
There may be other caching solutions, it's worth investigating!
Additional context
I don't expect the total size of the saved data to become computationally prohibitive; we don't generally have ridiculously large arrays.