|
| Re: Agent Controller needed for local profiling? [message #40258 is a reply to message #40112] |
Mon, 14 November 2005 12:45   |
 Paul Slauenwhite
Messages: 975
Registered: July 2009 |
Senior Member |
|
|
Hi Andreas,
Great news! In TPTP v4.1, the new Integrated Agent Controller (IAC)
eliminates the need for the Agent Controller for local profiling,
statistical monitoring and test execution. The IAC is automatically
installed when the TPTP workbench is installed. The IAC is available
on-demand when the Agent Controller is not running. When profiling or
statistical monitoring, select the 'Local Direct Connection' from the Hosts
list. Test execution automatically defaults to using the IAC for local
deployments when the Agent Controller is not running. For more information,
consult the 'New and Noteworthy' document for TPTP v4.1
(http://www.eclipse.org/tptp/ >> Documentation >> Installation and Getting
Started Guides >> New and Noteworthy >> 4.1.0).
The JRE configured in the serviceconfig.xml is required for launching
remote Java processes in profiling mode through the TPTP workbench. When a
Java process is launched and profiled via the Agent Controller, the JVM
configured in the following Application entry is used:
<Application configuration="default" executable="java.exe"
location="%SYS_TEMP_DIR%" path="%JAVA_PATH%"/>
Noteworthy, the 'jvm' attribute in the root AgentControllerConfiguration
element of the serviceconfig.xml is required for internal purposes.
Paul
"Andreas Schildbach" <andreas@schildbach.de> wrote in message
news:dl342v$vhd$1@news.eclipse.org...
> Hello everyone,
>
> will the Agent Controller be needed all time in the future?
>
> I consider it a bit cumbersome to run a separate program/process just
> for profiling an application locally inside Eclipse.
>
> If locally debugging is possible without Agent Controller, why isn't
> locally profiling?
>
> I also do not understand which JRE I have to configure in
> serviceconfig.xml: Does it have to be same I have configured in the
> application properties? What if I'm profiling two different apps using
> different JREs at the same time?
>
> Regards,
>
> Andreas
|
|
|
| Re: Agent Controller needed for local profiling? [message #40280 is a reply to message #40258] |
Mon, 14 November 2005 15:26 |
Marius Slavescu
Messages: 67
Registered: July 2009 |
Member |
|
|
Hi Andreas,
The TPTP 4.1 release has not been announced yet, so please check in a few
days for the document that Paul has mentioned.
Although IAC will allow you to do locally most of what you can do with the
Agent Controller (AC), if you need to profile locally an application (which
will result in a lot of profiling data) I would recommend you to still use
the full blown Agent Controller (because of time constrains in 4.1, the
performance improvements were deferred to 4.2, where we will focus on
improving the performance of IAC so it will match AC for local scenarios).
Regards,
Marius
"Paul Slauenwhite" <paules@ca.ibm.com> wrote in message
news:dla0ta$1t6$1@news.eclipse.org...
> Hi Andreas,
> Great news! In TPTP v4.1, the new Integrated Agent Controller (IAC)
> eliminates the need for the Agent Controller for local profiling,
> statistical monitoring and test execution. The IAC is automatically
> installed when the TPTP workbench is installed. The IAC is available
> on-demand when the Agent Controller is not running. When profiling or
> statistical monitoring, select the 'Local Direct Connection' from the
Hosts
> list. Test execution automatically defaults to using the IAC for local
> deployments when the Agent Controller is not running. For more
information,
> consult the 'New and Noteworthy' document for TPTP v4.1
> (http://www.eclipse.org/tptp/ >> Documentation >> Installation and Getting
> Started Guides >> New and Noteworthy >> 4.1.0).
>
> The JRE configured in the serviceconfig.xml is required for launching
> remote Java processes in profiling mode through the TPTP workbench. When
a
> Java process is launched and profiled via the Agent Controller, the JVM
> configured in the following Application entry is used:
>
> <Application configuration="default" executable="java.exe"
> location="%SYS_TEMP_DIR%" path="%JAVA_PATH%"/>
>
> Noteworthy, the 'jvm' attribute in the root
AgentControllerConfiguration
> element of the serviceconfig.xml is required for internal purposes.
>
> Paul
>
> "Andreas Schildbach" <andreas@schildbach.de> wrote in message
> news:dl342v$vhd$1@news.eclipse.org...
> > Hello everyone,
> >
> > will the Agent Controller be needed all time in the future?
> >
> > I consider it a bit cumbersome to run a separate program/process just
> > for profiling an application locally inside Eclipse.
> >
> > If locally debugging is possible without Agent Controller, why isn't
> > locally profiling?
> >
> > I also do not understand which JRE I have to configure in
> > serviceconfig.xml: Does it have to be same I have configured in the
> > application properties? What if I'm profiling two different apps using
> > different JREs at the same time?
> >
> > Regards,
> >
> > Andreas
>
>
|
|
|
Powered by
FUDForum. Page generated in 2.91862 seconds
] 
Search
Help
Register
Login
Home
