[Paraview] Unreclaimed memory in coprocessing? (PV 3.12.0 and git-master)
Takuya OSHIMA
oshima at eng.niigata-u.ac.jp
Tue Jan 10 11:43:59 EST 2012
Hi John,
What I observed on a Mac and a Linux box with 8 processor parallel
runs (around 400MB per process) were quite similar to your memory
profiling but with a bit larger growth rate of 1-2% and 2-3% per
coprocessing execution respectively (somehow it was bigger on Linux).
I'll see if I can do similar profiling.
Takuya OSHIMA, Ph.D.
Faculty of Engineering, Niigata University
8050 Ikarashi-Ninocho, Nishi-ku, Niigata, 950-2181, JAPAN
From: "Biddiscombe, John A." <biddisco at cscs.ch>
Subject: RE: [Paraview] Unreclaimed memory in coprocessing? (PV 3.12.0 and git-master)
Date: Tue, 10 Jan 2012 14:51:41 +0000
> Takuya
>
> Running a test of coprocessing on a very small simulation using just 2 cores
> on the desktop, I am seeing what looks like a very small leak. Over about 30
> iterations, it’s of the order of 30MB, so might not be real (need to test on a
> bigger domain to see if it grows faster), but the trend looks credible. I’ll
> see if I can pinpoint where the loss is occurring.
>
> JB
>
> [cid]
>
> -----Original Message-----
> From: paraview-bounces at paraview.org [mailto:paraview-bounces at paraview.org] On
> Behalf Of Takuya OSHIMA
> Sent: 10 January 2012 15:11
> To: paraview at paraview.org
> Subject: Re: [Paraview] Unreclaimed memory in coprocessing? (PV 3.12.0 and
> git-master)
>
> Attached in the previous mail is a sample Python coprocessing script that
> exhibits the problem (written by the coprocessing script generator of
> git-master as of today).
>
> Takuya
>
> Takuya OSHIMA, Ph.D.
>
> Faculty of Engineering, Niigata University
>
> 8050 Ikarashi-Ninocho, Nishi-ku, Niigata, 950-2181, JAPAN
>
> From: Takuya OSHIMA <oshima at eng.niigata-u.ac.jp>
>
> Subject: Unreclaimed memory in coprocessing? (PV 3.12.0 and git-master)
>
> Date: Tue, 10 Jan 2012 23:08:21 +0900 (JST)
>
> > Hi,
>
> >
>
> > I am having a problem where the memory usage of my simulation program
>
> > which links with the PV coprocessing library grows until it gets
>
> > killed by the operating system.
>
> >
>
> > I have the following piece of code for triggering coprocessing and if
>
> > I watch the memory usage with the ps/top commands it grows only at the
>
> > timestep where this->Processor->CoProcess() is called. My simulation
>
> > program uses vtkImageData as underlying data structure so no data
>
> > format adaptation (that may involve allocating extra memory for data
>
> > copy) is performed.
>
> >
>
> > this->DataDescription->SetTimeData(this->TimeInfo->GetTimeValue(),
>
> > this->TimeInfo->GetTIter());
>
> > if (this->Processor->RequestDataDescription(this->DataDescription))
>
> > {
>
> > vtkCPInputDataDescription *idd
>
> > = this->DataDescription->GetInputDescriptionByName("input");
>
> > // obtain vtkImageData to coprocess from my simulation program
>
> > vtkImageData *grid = this->TimeInfo->GetGrid();
>
> > idd->SetWholeExtent(grid->GetWholeExtent());
>
> > idd->SetGrid(grid);
>
> > // now call the coprocessing library
>
> > this->Processor->CoProcess(this->DataDescription);
>
> > }
>
> >
>
> > Besides, the Apple's "leaks" tool shows no meaningful leaks which
>
> > makes me wonder if e.g. there are un-unregistered proxies than simply
>
> > unmatched New()/Delete() or new/delete pairs.
>
> >
>
> > The problem is same for PV 3.12.0 and the git master as of today.
>
> > Is anybody else having the problem? Any ideas?
>
> >
>
> > Thanks,
>
> > Takuya
>
> >
>
> > Takuya OSHIMA, Ph.D.
>
> > Faculty of Engineering, Niigata University
>
> > 8050 Ikarashi-Ninocho, Nishi-ku, Niigata, 950-2181, JAPAN
>
> _______________________________________________
>
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/
> opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at: http://
> paraview.org/Wiki/ParaView
>
> Follow this link to subscribe/unsubscribe:
>
> http://www.paraview.org/mailman/listinfo/paraview
>
> *
>
More information about the ParaView
mailing list