Skip to main content



      Home
Home » Archived » Test and Performance Tools Platform (TPTP) » TPTP trace.trcxml notation format new agent controller 4.3
TPTP trace.trcxml notation format new agent controller 4.3 [message #91028] Wed, 10 January 2007 07:06 Go to next message
Eclipse UserFriend
Originally posted by: baesjou.tid.es

Hi,
I want to play around with the trace.trcxml and use/parse some stuff out
of it and link it to other data. However I am a bit puzzled about the time
notation format.

In the first part of the trace file:
<?xml version="1.0"?>
<TRACE>
<node nodeId="" hostname="localhost" ipaddress="127.0.0.1" timezone="-60"
time="1168431557.827301979"/>
<processCreate processId="78b7eb83-a20f-4a87-bf6d-9a418e6426fc"
pid="22985" nodeIdRef="" time="1168431557.827301979"/>
<agentCreate agentId="045b7246-0493-46a7-9ef4-0663db784a06"
version="2.000" processIdRef="78b7eb83-a20f-4a87-bf6d-9a418e6426fc"
agentName="org.eclipse.tptp.jvmti" agentType="Profiler"
agentParameters="server=standalone" time="1168431557.827301979"/>
<traceStart traceId="409267cd-dfad-4c3e-8a1a-8c038ba0f4a7"
agentIdRef="045b7246-0493-46a7-9ef4-0663db784a06"
time="1168431557.827538013"/>

There are clearly some "unix" time stamps, which can be therefore be
linked to other files generated on the same machine with similar
timestamps. But now at the point where it is going to track objects it
suddenly prints:

<threadStart threadId="1" time="19615175628.096279144"
threadName="Reference Handler" groupName="system" parentName=""/>
<threadStart threadId="2" time="19615175628.096366882"
threadName="Finalizer" groupName="system" parentName=""/>

Which are timestamps at the end of the 32bit lifetime in 2038.... they are
not very useful. Is this a unwanted "feature" or am I missing out on
something?

Help would be appreciated.

Best regards,
Bertrand
Re: TPTP trace.trcxml notation format new agent controller 4.3 [message #91044 is a reply to message #91028] Wed, 10 January 2007 09:10 Go to previous messageGo to next message
Eclipse UserFriend
Hi Bertrand,

Which operating system and processor architecture are you using?

In general, the timestamps are indeed an OS timestamps (Unix in your
case). If you are using Linux on IA-32, the timestamp issues you see are
probably related to the following bug:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=165190

If this is the case, you may want to check the latest binaries
(currently under development for TPTP 4.4) in the following link:
http://www.eclipse.org/downloads/download.php?file=/tptp/4.4 .0/dev/TPTP-4.4.0-200701080100/javaprofiler.linux_ia32-TPTP- 4.4.0-200701080100.zip

I believe the problem was addressed in this build.

HTH,
Asaf

--
Asaf Yaffe
Eclipse TPTP Committer, JVMTI Profiler
Re: TPTP trace.trcxml notation format new agent controller 4.3 [message #91113 is a reply to message #91044] Thu, 11 January 2007 07:21 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: baesjou.tid.es

Hi Asaf,

Thanks, this was indeed the problem. I have one other question in the
format of the trcxml file, the size="80" element, is this in bits or in
bytes?

I am producing some nice graphs now how memory usage evolves over time,
using some scripts pulling out data and feeding it to gnuplot. If anyone
is interested I can offcourse post them once they are more or less usable.
However no nice workbench integration or something.....

Best regards,
Bertrand
Re: TPTP trace.trcxml notation format new agent controller 4.3 [message #91128 is a reply to message #91113] Thu, 11 January 2007 07:59 Go to previous messageGo to next message
Eclipse UserFriend
Bertrand wrote:
> Hi Asaf,
>
> Thanks, this was indeed the problem. I have one other question in the
> format of the trcxml file, the size="80" element, is this in bits or in
> bytes?
>

The "size" attribute in in bytes.

> I am producing some nice graphs now how memory usage evolves over time,
> using some scripts pulling out data and feeding it to gnuplot. If anyone
> is interested I can offcourse post them once they are more or less
> usable. However no nice workbench integration or something.....
>
> Best regards,
> Bertrand
>

Sounds interesting. Keep us updated.

Thanks!
Asaf

--
Asaf Yaffe
Eclipse TPTP Committer, JVMTI Profiler
Re: TPTP trace.trcxml notation format new agent controller 4.3 [message #91475 is a reply to message #91028] Thu, 18 January 2007 08:21 Go to previous message
Eclipse UserFriend
See
http://www.eclipse.org/tptp/platform/documents/resources/pro filingspec/XML4Profiling.htm
for more details on the format of the Event Specification for Java Profiling
(AKA trace.trcxml).

Paul
"Bertrand" <baesjou@tid.es> wrote in message
news:2a7f670db639f9a679d363a506ab87ad$1@www.eclipse.org...
> Hi,
> I want to play around with the trace.trcxml and use/parse some stuff out
> of it and link it to other data. However I am a bit puzzled about the time
> notation format.
>
> In the first part of the trace file:
> <?xml version="1.0"?>
> <TRACE>
> <node nodeId="" hostname="localhost" ipaddress="127.0.0.1" timezone="-60"
> time="1168431557.827301979"/>
> <processCreate processId="78b7eb83-a20f-4a87-bf6d-9a418e6426fc"
> pid="22985" nodeIdRef="" time="1168431557.827301979"/>
> <agentCreate agentId="045b7246-0493-46a7-9ef4-0663db784a06"
> version="2.000" processIdRef="78b7eb83-a20f-4a87-bf6d-9a418e6426fc"
> agentName="org.eclipse.tptp.jvmti" agentType="Profiler"
> agentParameters="server=standalone" time="1168431557.827301979"/>
> <traceStart traceId="409267cd-dfad-4c3e-8a1a-8c038ba0f4a7"
> agentIdRef="045b7246-0493-46a7-9ef4-0663db784a06"
> time="1168431557.827538013"/>
>
> There are clearly some "unix" time stamps, which can be therefore be
> linked to other files generated on the same machine with similar
> timestamps. But now at the point where it is going to track objects it
> suddenly prints:
>
> <threadStart threadId="1" time="19615175628.096279144"
> threadName="Reference Handler" groupName="system" parentName=""/>
> <threadStart threadId="2" time="19615175628.096366882"
> threadName="Finalizer" groupName="system" parentName=""/>
>
> Which are timestamps at the end of the 32bit lifetime in 2038.... they are
> not very useful. Is this a unwanted "feature" or am I missing out on
> something?
>
> Help would be appreciated.
>
> Best regards,
> Bertrand
>
>
Previous Topic:JUnit4
Next Topic:codereview for C++
Goto Forum:
  


Current Time: Tue Jul 01 03:23:15 EDT 2025

Powered by FUDForum. Page generated in 0.04240 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top