[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [platform-core-dev] RE: core.resources Performance Test question
|
Hi again,
I thought a bit more about this, and I am afraid that the way
the test (WorkspacePerformanceTest#testRefreshProject())
is written today, the heap size data will not at all
help me.
Right now, heap size is measured after the test completes;
but in my case (Refresh resources), memory consumption is
temporary during the algorithm. In other words, the algorithm
needs a lot of memory, but once the computation is done the
memory is returned for garbage collection so the value after
the test is not interesting.
I assume that there are many other similar cases, so perhaps
somebody has an idea for how to measure memory consumption in
this situation?
Right now, my feeling ist that the only reliable and realistic
way to measure memory consumption is running the test in a
separate VM process with varying memory limits set by -Xmx
vm argument, until the test runs into an OutOfMemoryException.
This seems to be the only way how garbage collection can be
taken into account, coming up with a value that matters for
end users.
Has anybody tried this before? Or how else could I get
realistic data for memory consumption?
Cheers,
--
Martin Oberhuber, Senior Member of Technical Staff, Wind River
Target Management Project Lead, DSDP PMC Member
http://www.eclipse.org/dsdp/tm
> -----Original Message-----
> From: platform-core-dev-bounces@xxxxxxxxxxx
> [mailto:platform-core-dev-bounces@xxxxxxxxxxx] On Behalf Of
> Oberhuber, Martin
> Sent: Friday, October 16, 2009 5:33 PM
> To: Frederic Fusier
> Cc: Eclipse Platform Core component developers list.; John
> Arthorne; Boris Bokowski
> Subject: [platform-core-dev] RE: core.resources Performance
> Test question
>
> Hi Frederic,
>
> > BTW, I had a look on my tool and saw that it was not too
> > costly to finalize the implementation to display a new number
>
> that is great! - But I don't think I'll need the pages for the
> latest I-build since I'll want to compare an upcoming N-build
> or I-build on the official performance machines against the
> baseline anyways. So it'll be sufficient if that upcoming
> N-build or I-build has the new number (heapsize) displayed
> for both the new build and the previous baseline.
>
> > Would it be possible to open a bug for this against
> > Platform/Releng in order to track the work around this?
>
> You are welcome:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=292545
>
> Cheers,
> --
> Martin Oberhuber, Senior Member of Technical Staff, Wind River
> Target Management Project Lead, DSDP PMC Member
> http://www.eclipse.org/dsdp/tm
