Ticket #168 (new todo)

Opened 3 years ago

Last modified 3 years ago

identify classes to use mpool based allocation

Reported by: ichthyo Owned by:
Priority: lesser Milestone: 2beta
Component: lumiera Keywords: QA
Cc: Blocked By: #167
Blocking: #130

Description

This is a QA ticket for later

Indeed we need a more clear understanding of the actual inner workings before we can consider to target this ticket. Blindly inserting custom operator new into a ton of classes wouldn't be helpful (and might be a dangerous undertaking btw). Instead, we should identify which classes are

  • small allocations
  • indeed heap allocated most of the time
  • created and deleted in great numbers

the MObject hierarchy would be a good candidate, to give an example.

Change History

comment:1 Changed 3 years ago by ichthyo

  • Blocking 130 added

comment:2 Changed 3 years ago by ichthyo

Just for sake of clarity: the most important allocation problem within proc layer is already covered by AllocationCluster (which in turn is expected to use mpool as a backend (see #101). Thus this ticket is not about solving an urgent performance problem, but for improving the overall situation (thus the lesser priority)

Note: See TracTickets for help on using tickets.