|Message: Re: memory leak in exrdm||Not Logged In (login)|
Click on the Forum title, e.g. on the "Forums by Category" page, to read a sequence of postings to the Forum and its threads all in one page. If you are only interested in one thread or the thread following a specific posting, click the thread or the posting, which takes you to a smaller page, which contains only the part you are interested in and may be easier to navigate.
Messages are "chained" if there are only replies at the first level, i.e. 1/1.html, 1/1/1.html etc. In case of "chained" messages the message number is replaced by the icon and there is no indentation.
Inline: Display the subject line only or also the text of the posting(s); for the choice "All" the "Outline" choices are switched off.
|1||0||1||no text / full text of posting|
|2||1||All||text for level 1 only / text for All postings|
Outline: Choose the depth of the posting thread, successive toggle controls provide increasing detail.
|1||2||1||2 levels / 1 level (original posting)|
|2||3||2||3 levels / 2 levels|
|3||3||All||3 levels / all levels (all postings)|
This is most likely NOT a memory leak, but due to the increase in size of memory based tuples created in the application.
Below some offline discussions on this issue:
sorry for the late answer, too many other things (as usual) :-(
For the XML format we have discussed in AIDA and found no way to do the kind of "flushing" of buffers like other tools can do using a proprietary format. The XML files (esp. the compressed ones) are streams which are not buffered. So the only way of doing this is to split them in several files ("chaining" these on reading back) which will have to have an "arbitrary" ways of setting the names from the original one.
On the other hand this can be easily done by the user through a little helper (opening another tree, copying the tuple to the new tree, closing the new tree, resetting the tuple on the original one). This way also the frequency of writing out (i.e. the number of files) is under control of the user.
I'm not sure if this answers your question, please let me know if not ....
> Forwarded is a discussion on possible memory leaks. One explanation is > the increased size of ntuples in memory as the simulation progresses. > > My memory with HBOOK is that the memeory based data file is > automatically > flushed out after it reached a certain size. I don't know how this > issue > is handled in AIDA/PI. > > Fan > > -----Original Message----- > From: Fan Lei > Sent: Thursday, July 21, 2005 9:14 AM > To: 'Hall, Carter R.' > Subject: RE: exrdm > > > The increased usage of memory for esrdm is more likely due to the > fact that in this example the information collected after each event > are being hold in the memory and they are written disk files only at > the > end of each run. As a number of tuples are filled at the end of each > event in addition to histograms, the size of the data in memory goes up > after each event... > > For real applications with large data file to be created, one has to > dump > the tuples to disk files after every certain number of events, or > after the > memory based data size reached a critical value. This is the case for > the > old HBOOK data package. I would execpect similar function exists in the > AIDA implementations. > > Fan >
|Inline Depth:||Outline Depth:||Add message:|