From: Robert A Duff <bobduff@shell01.TheWorld.com>
Subject: Re: Memory profiling
Date: 27 May 2005 11:24:15 -0400
Date: 2005-05-27T11:24:15-04:00 [thread overview]
Message-ID: <wccll6066ao.fsf@shell01.TheWorld.com> (raw)
In-Reply-To: 429717E8.6030806@mailinator.com
"Alex R. Mosteo" <devnull@mailinator.com> writes:
> I suppose something similar can be achieved using distinct storage pools
> for each access type being tracked, but I find this more
> inconvenient. Ummm, maybe a type holding a list of storage pools created
> on demand...
All those storage pools can share the same underlying memory pool. That
is, each pool just keeps track of whatever debugging/statistics info you
want, and then calls some underlying pool, or just does a "new", or
calls malloc, or whatever. So gathering fine-grained (per type)
information does not need to imply that you have to actually allocate
type-segregated data.
- Bob
next prev parent reply other threads:[~2005-05-27 15:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-27 12:51 Memory profiling Alex R. Mosteo
2005-05-27 15:24 ` Robert A Duff [this message]
2005-05-27 15:55 ` Alex R. Mosteo
2005-05-27 16:27 ` Alex R. Mosteo
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox