[xsd-users] in memory footprint

[Rizzuto, Raymond]

I added the instrumentation code to a simple test app I have that creates a simpleOrder.  Here are the printouts after the creation of the simple order, and afterward its destruction:

Creation:
allocate:
  count: 1199
  bytes: 5314880

free:
  count: 954
  bytes: 3715352

Destruction:
allocate:
  count: 1199
  bytes: 5314880

free:
  count: 1191
  bytes: 5305740


Based on the creation counts, it does look like the simpleOrder is holding on to ~1.2meg of memory, which jibes with the growth I saw in the process size.

I need to look into why there are 8 allocations that aren't freed once the simpleOrder goes away - that is a bit disturbing, although 2 orders of magnitude smaller than the size of the simpleOrder.

Ray

-----Original Message-----
From: Boris Kolpackov [mailto:boris at codesynthesis.com]
Sent: Friday, October 10, 2008 10:19 AM
To: Rizzuto, Raymond
Cc: xsd-users at codesynthesis.com
Subject: Re: [xsd-users] in memory footprint

Hi Ray,

Rizzuto, Raymond <Raymond.Rizzuto at sig.com> writes:

> The slow exit was all the static allocations being deallocated,
> and the memory tracker not finding them because of the mem_reset's.

Yes, it is a very crude memory profiler ;-). It slows down memory
allocations/deallocations significantly due to the linear search
used in mem_map. The speed of the test shouldn't be used as any
kind of indication of what it will be in the actual application.

Boris


IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.