Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Martini Framework Design Overview"
| Line 9: | Line 9: | ||
*JPI: Java Profiling function.. | *JPI: Java Profiling function.. | ||
*JIE: Java instrumentation function. | *JIE: Java instrumentation function. | ||
| − | *Instrumentation Adaptor: | + | *Instrumentation Adaptor: Instrumentation adaptors for call graph profiling (CGAdaptor), heap profiling (HeapAdaptor) and thread profiling (ThreadAdaptor). |
Revision as of 05:38, 20 November 2009
Introduction
Martini framework is designed to cover different runtime environments Java VM and .NET CLR initially. Actually it mainly used for JVMTI on Java VM now. It also provides framework users an unified interface for different profilers based on MPI(Martini Profiling Interface).
There are five basic components in Martini internally. They are:
- MartiniOSA: This component is used to abstract common OS functions. Such as I/O and threads related functions are included.
- JPIBootLoader & LibraryLoader: They will load different components dynamically.
- JPI: Java Profiling function..
- JIE: Java instrumentation function.
- Instrumentation Adaptor: Instrumentation adaptors for call graph profiling (CGAdaptor), heap profiling (HeapAdaptor) and thread profiling (ThreadAdaptor).