Object pools
shindavid opened this issue · 1 comments
shindavid commented
Currently, Node objects and NNEvaluation objects are constructed and destroyed via new and delete. It would be more efficient to use object pools.
The details of this are quite sensitive, due to multi-threading, block allocations, and smart-pointer usage.
Issue #42 should be resolved first, as that change will affect memory allocation/deallocation patterns.
shindavid commented
Finally completed. Node/edge objects now come from an object pool, without needing any smart-pointer mechanics.