Difference: ATeamDataContainers (5 vs. 6)

Revision 62007-04-03 - unknown

Line: 1 to 1
 
META TOPICPARENT name="TrackATeam"

Data Containers for Track Discussions

Line: 68 to 68
 This is effectively the approach I believe used in the Tsa world, where no private memory management is used but simply that provided by the Gaudi framework.

Note that the topic of overloading new and delete is a very well know and discussed problem. Most C++ books will mention it at some point or a quick google search will lead you to many many pages discussing the issue.

Changed:
<
<
In addition there exists many well tested and proven solutions to speed things up, such as the memory pool. In many was this is very similar to the solution adopted by the PatDataStore, in that a pool of memory is reserved, and when new is called the system simply takes some memory from the pool. When the object is finally deleted the memory is given back to the pool.
>
>
In addition there exists many well tested and proven solutions to speed things up, such as the memory pool. In many ways this is similar to the solution adopted by the PatDataStore, in that a pool of memory is reserved and when new is called the system simply takes some memory from the pool. When the object is finally 'deleted' the memory is simply given back to the pool.
  In the most recent versions of GOD, all event model classes have been using a memory pool implementation from boost to overload new and delete.
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback