Chris has been doing some sandbox work around the general problem Eclipse users and developers have with memory consumption. This is a logical extension of the XRay sandbox. He has created a small utility component called the memory manager, and the people that have been aware of his prototyping want to start leveraging it as they build on top of 3.2. It is JVM specific at this time but still of great value.
Chris has checked the code into CVS, but we want to make it available as a stand-alone feature, a tech preview for now. If things go well we may propose to make this part of the 4.2 GA depending on the consumer demand, which appears to already be growing. Chris will naturally fully support this work and Hubert is working to get the build in place within the next week. At this stage this work implies 2 new TPTP plugins and a new feature. I don't believe we need to create a new component entry in the project matrix but this should be managed as part of the trace project along with the XRay work.
We will formalize this with an enhancement request and an AG review next week. This note is to make people aware of the work, and get the ball rolling on any other PMC/RG/PG reviews that may be needed.
Thanks for your time.
--------------------------------------------------------------------------
Harm Sluiman, STSM,
phone:905-413-4032 fax: 4920
cell: 1-647-300-4758
mailto:[EMAIL PROTECTED]
Admin : Arlene Treanor [EMAIL PROTECTED] Tie: 969-2323 1-905-413-2323
----- Forwarded by Harm Sluiman/Toronto/IBM on 01/20/2006 07:54 AM -----
| Chris Laffra/Durham/[EMAIL PROTECTED]
01/18/2006 12:56 PM
|
|
Hi Hubert,
Harm and I talked about the following this morning:
The plan is to add a Memory Manager plugin to TPTP to monitor memory consumption in Eclipse, in particular to control the existence and contents of caches.
Here is a description (also for Harm):
The TPTP Cache Manager (org.eclipse.tptp.trace.memory) is a placeholder to register caches.
A cache is a datastructure that holds a temporary result that is typically calculated multiple times. To avoid repetitive computation and I/O, the intermediate result can be saved in a cache, so that future operations become faster. Each plugin implements its own policy on cache management, and in practice it is complicated to coordinate the various caches in a global manner. The end result is that the heap consumption of Eclipse-based applications can grow in an sometimes unbounded fashion.
What the cache manager does is registering caches in a meta-cache. Plugins can register and unregister caches at will. The manager does not implement a cache flushing policy itself.
The TPTP Cache Manager UI (org.eclipse.tptp.trace.memory.ui) shows all currently registered caches in a table and allows the end-user to observe them and to flush the caches.
With a more evolved cache policy, flushing could happen automatically when memory gets really low, for instance. In that case, the UI becomes optional and will be of most importance to developers.
Memory consumption is one of the hardest problems in large application development, including Eclipse IDEs, and a centralized cache manager definitely helps.
I just released to TPTP/trace a new feature for the so-called Memory Manager. The idea is to generate an isolated feature:
Much obliged,
Chris Laffra
Rational Performance Engineering Team
Email: [EMAIL PROTECTED]
http://eclipsefaq.org/chris
_______________________________________________ tptp-tracing-profiling-tools-dev mailing list tptp-tracing-profiling-tools-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/tptp-tracing-profiling-tools-dev
