Apr 25, 2019

About

Traces

Tools

Links

edit SideBar

Search

WikiSandbox

Main.WikiSandbox History

Hide minor edits - Show changes to output

July 10, 2009, at 08:57 PM by 129.88.69.207 -
Changed line 29 from:
|| border=1
to:
|| border=1 width=100%
Changed line 37 from:
|| border=1
to:
|| border=1 width=100%
Changed line 56 from:
|| border=1
to:
|| border=1 width=100%
Changed line 69 from:
|| border=1
to:
|| border=1 width=100%
Changed line 80 from:
|| border=1
to:
|| border=1 width=100%
Changed line 90 from:
|| border=1
to:
|| border=1 width=100%
Changed line 102 from:
|| border=1
to:
|| border=1 width=100%
July 10, 2009, at 08:56 PM by 129.88.69.207 -
Changed lines 3-4 from:
The trace format is organized hierarchically as follows:
to:
The trace format is organized hierarchically as follows:\\
July 10, 2009, at 08:55 PM by 129.88.69.207 -
Changed lines 3-4 from:
The trace format is organized hierarchically as follows:
to:
The trace format is organized hierarchically as follows:
July 10, 2009, at 08:54 PM by 129.88.69.207 -
Changed lines 92-107 from:
||event_state ||event_id
unique ID of event state

component_id
unique ID for this component trace data
node_id
unique ID for this node

platform_id
ID of
platform that is the node parent
i_val
integer
f_val
float (for example, 0% - 100% for CPU
availability)
s_val
string
to:
||event_id ||unique ID of event state||
||
component_id ||unique ID for this component trace data||
||
node_id ||unique ID for this node ||
||
platform_id ||ID of platform that is the node parent||
||node
_name ||name of node||
||event_type ||type of event (0 -> unavailability, 1->
availability). Event id's up to 10,000 are reserved; the rest can be user defined ||
||event
_start_time ||start of this event (UNIX epoch time)||
||event_end_time ||end of this event (UNIX epoch time) ||
||event_end_reason ||reason the event type or state changed at the end of this trace (for example, reason that CPU became unavailable: 0=undefined, 1=miscellaneous, 2=mouse_activity, 3=keyboard_activity, 4=scheduled_downtime, 5=graceful_shutdown, 6=hard_shutdown)||

|| border=1
||! '''event_state''' !||
||event_id ||unique ID of event state ||
||component_id ||unique ID for this component trace data ||
||node_id ||unique ID for this node ||
||platform_id ||ID of platform that is the node parent||
||i_
val ||integer ||
||f_val ||float (for example, 0% - 100% for CPU availability)||
||s_val ||string||
July 10, 2009, at 08:49 PM by 129.88.69.207 -
Added lines 68-107:

|| border=1
||! '''component''' !||
||component_id ||unique ID for this component ||
||node_id ||ID of the node containing this component ||
||platform_id ||ID of platform containing this node ||
||node_name ||Name of the node||
||component_type ||type of this component trace (0 -> host availability, network, CPU, client, memory, etc) ||
||trace_start ||when the trace event first appeared (epoch time)||
||trace_end ||when the trace event last appeared (epoch time)||
||resolution ||resolution of the traces in seconds||

|| border=1
||! '''creator''' !||
||creator_id ||ID of creator of this component trace data ||
||component_id ||unique ID for this component trace data ||
||node_id ||ID of the node corresponding to this trace ||
||platform_id ||ID of platform containing node||
||creator ||name(s) of the person(s) who recorded the event traces||
||cite ||citation (bibtex, etc) for using the data from the event traces ||
||copyright ||details of the copyright and rights reserved||

|| border=1
||! '''event_trace''' !||
||event_state ||event_id
unique ID of event state

component_id
unique ID for this component trace data
node_id
unique ID for this node

platform_id
ID of platform that is the node parent
i_val
integer
f_val
float (for example, 0% - 100% for CPU availability)
s_val
string
July 10, 2009, at 08:12 PM by 129.88.69.207 -
Changed line 30 from:
|| !'''platform''' !||
to:
||! '''platform''' !||
Changed line 38 from:
|| !'''node''' !||
to:
||! '''node''' !||
Changed line 57 from:
|| !'''node_perf''' !||
to:
||! '''node_perf''' !||
July 10, 2009, at 08:11 PM by 129.88.69.207 -
Changed line 30 from:
||!'''platform''' !||
to:
|| !'''platform''' !||
Changed line 38 from:
||!'''node''' !||
to:
|| !'''node''' !||
Changed line 57 from:
||!'''node_perf''' !||
to:
|| !'''node_perf''' !||
July 10, 2009, at 08:11 PM by 129.88.69.207 -
Changed line 30 from:
||! '''platform''' !||
to:
||!'''platform''' !||
Changed line 38 from:
||! '''node''' !||
to:
||!'''node''' !||
Added lines 55-68:

|| border=1
||!'''node_perf''' !||
||metric_id ||unique ID for performance metric (benchmark)||
||component_id ||unique ID for the component||
||node_id ||unique ID for this node ||
||platform_id ||ID of platform containing node ||
||sfpop_speed ||maximum single precision floating point speed (ops/sec)||
||dfpop_speed ||maximum double precision floating point speed (ops/sec)||
||iop_speed ||integer operation speed (ops/sec)||
||i_val ||integer ||
||f_val ||float ||
||s_val ||string||
July 10, 2009, at 08:08 PM by 129.88.69.207 -
Changed lines 45-46 from:
||proc_model || processor name, model, version number||
||os_name || name and version of the resource OS ||
to:
||proc_model ||processor name, model, version number||
||os_name ||name and version of the resource OS ||
July 10, 2009, at 08:07 PM by 129.88.69.207 -
Changed lines 39-58 from:
||node_id ||unique ID for this node ||
to:
||node_id ||unique ID for this node ||
||platform_id ||id of the platform containing node ||
||node_name ||name of node||
||node_ip ||IP address ||
||node_location ||location of the node (e.g. country, geographic coordinates)
||timezone ||time zone of the resource (second offset from GMT)||
||proc_model || processor name, model, version number||
||os_name || name and version of the resource OS ||
||cores_per_proc ||number of cores per processor ||
||num_procs ||number of processors for this node||
||mem_size ||number of bytes of memory ||
||disk_size ||number of bytes of disk space||
||up_bw ||number of bytes/sec of upload speed ||
||down_bw ||number of bytes/sec of download speed ||
||metric_id ||unique ID for performance metric (e.g. benchmark) ||
||notes ||other notes related to this resource||


July 10, 2009, at 08:03 PM by 129.88.69.207 -
Changed lines 31-36 from:
|| platform_id || A unique number identifying this platform. >> It allows one to differentiate pools of nodes.||
|| platform_name || name of the platform (e.g. "Berkeley_NOW_Lab_Fall_1998") ||
|| platform_location || location name of the platform source (e.g. "Berkeley NOW Lab - Soda Hall 2nd Floor, USA, Planet Earth") ||
|| platform_type || type of the platform (cluster, multicluster, grid, desktop_grid, or volunteer_computing) ||
|| misc_notes || miscellaneous notes ||
to:
||platform_id ||A unique number identifying this platform. >> It allows one to differentiate pools of nodes.||
||platform_name ||name of the platform (e.g. "Berkeley_NOW_Lab_Fall_1998") ||
||platform_location ||location name of the platform source (e.g. "Berkeley NOW Lab - Soda Hall 2nd Floor, USA, Planet Earth") ||
||platform_type ||type of the platform (cluster, multicluster, grid, desktop_grid, or volunteer_computing) ||
||misc_notes ||miscellaneous notes ||
Changed line 39 from:
|| node_id || unique ID for this node ||
to:
||node_id ||unique ID for this node ||
July 10, 2009, at 08:01 PM by 129.88.69.207 -
Changed lines 30-32 from:
||! '''paltform''' !||
|| platform_id || A unique number identifying this platform.
It allows one to differentiate pools of nodes.||
to:
||! '''platform''' !||
|| platform_id || A unique number identifying this platform. >> It allows one to differentiate pools of nodes.||
Added lines 33-39:
|| platform_location || location name of the platform source (e.g. "Berkeley NOW Lab - Soda Hall 2nd Floor, USA, Planet Earth") ||
|| platform_type || type of the platform (cluster, multicluster, grid, desktop_grid, or volunteer_computing) ||
|| misc_notes || miscellaneous notes ||

|| border=1
||! '''node''' !||
|| node_id || unique ID for this node ||
July 10, 2009, at 07:57 PM by 129.88.69.207 -
Changed lines 31-32 from:
|| platform_id || A unique number identifying this platform.\\ It allows one to differentiate pools of nodes.||
to:
|| platform_id || A unique number identifying this platform.
It allows one to differentiate pools of nodes.||
July 10, 2009, at 07:57 PM by 129.88.69.207 -
Changed lines 31-32 from:
|| platform_id || A unique number identifiying this platform. It allows one to differentiate pools of nodes.||
|| cell 1 || cell 2 || cell 3 ||
to:
|| platform_id || A unique number identifying this platform.\\ It allows one to differentiate pools of nodes.||
|| platform_name || name of the platform (e.g. "Berkeley_NOW_Lab_Fall_1998") ||
July 10, 2009, at 07:56 PM by 129.88.69.207 -
Changed line 31 from:
||! platform_id ||! A unique number identifiying this platform. It allows one to differentiate pools of nodes.||
to:
|| platform_id || A unique number identifiying this platform. It allows one to differentiate pools of nodes.||
July 10, 2009, at 07:55 PM by 129.88.69.207 -
Added lines 28-32:

|| border=1
||! '''paltform''' !||
||! platform_id ||! A unique number identifiying this platform. It allows one to differentiate pools of nodes.||
|| cell 1 || cell 2 || cell 3 ||
July 10, 2009, at 07:53 PM by 129.88.69.207 -
Changed line 24 from:
---
to:
----
July 10, 2009, at 07:52 PM by 129.88.69.207 -
Changed line 24 from:
to:
---
July 10, 2009, at 07:51 PM by 129.88.69.207 -
Changed lines 10-14 from:
A '''platform''' (bold) contains a set of nodes. Examples of a platform include SETI@home, desktops at Microsoft.

A '''node''' (bold) contains a set of components, which is a software module or hardware resource of the node. Each node can have several components (e.g. CPU speed, availability memory, client availability), each of which has a corresponding trace.

A '''component''' (bold) describes attributes of a software module or hardware resource of a node.
to:
A '''platform''' contains a set of nodes. Examples of a platform include SETI@home, desktops at Microsoft.

A '''node''' contains a set of components, which is a software module or hardware resource of the node. Each node can have several components (e.g. CPU speed, availability memory, client availability), each of which has a corresponding trace.

A '''component''' describes attributes of a software module or hardware resource of a node.
Changed line 16 from:
'''component_perf''' (bold) is the component performance, as measured through benchmarks for example.
to:
'''component_perf''' is the component performance, as measured through benchmarks for example.
Changed lines 18-23 from:
A '''creator'''(bold) is the person responsible for the trace data set. This table stores details about citations and copyright.

An '''event_trace''' (bold) is the trace of an event, with all of corresponding timing information

'''event_state''' (bold) is the state corresponding to an event_trace. For example, for CPU availability, the event_state could be the idleness of the CPU. For host availability, it could be the monitoring information associated with the event.
to:
A '''creator''' is the person responsible for the trace data set. This table stores details about citations and copyright.

An '''event_trace''' is the trace of an event, with all of corresponding timing information

'''event_state''' is the state corresponding to an event_trace. For example, for CPU availability, the event_state could be the idleness of the CPU. For host availability, it could be the monitoring information associated with the event.
July 10, 2009, at 07:50 PM by 129.88.69.207 -
Changed lines 11-16 from:
A node contains a set of components, which is a software module or hardware resource of the node. Each node can have several components (e.g. CPU speed, availability memory, client availability), each of which has a corresponding trace.
A component describes attributes of a software module or hardware resource of a node.
component_perf is the component performance, as measured through benchmarks for example.
A creator is the person responsible for the trace data set. This table stores details about citations and copyright.
An event_trace is the trace of an event, with all of corresponding timing information
event_state is the state corresponding to an event_trace. For example, for CPU availability, the event_state could be the idleness of the CPU. For host availability, it could be the monitoring information associated with the event.
to:

A '''node''' (bold) contains a set of components, which is a software module or hardware resource of the node. Each node can have several components (e.g. CPU speed, availability memory, client availability), each of which has a corresponding trace.

A '''component''' (bold) describes attributes of a software module or hardware resource of a node.

'''component_perf''' (bold) is the component performance, as measured through benchmarks for example.

A '''creator'''(bold) is the person responsible for the trace data set. This table stores details about citations and copyright.

An '''event_trace''' (bold) is the trace of an event, with all of corresponding timing information

'''
event_state''' (bold) is the state corresponding to an event_trace. For example, for CPU availability, the event_state could be the idleness of the CPU. For host availability, it could be the monitoring information associated with the event.
July 10, 2009, at 07:48 PM by 129.88.69.207 -
Changed lines 1-3 from:
Feel free to use this page to experiment with the [[PmWiki/Text Formatting Rules]]. Just click the "Edit Page" link at the bottom of the page.
----
I just add some thing
to:
This document describes the Failure Trace Archive format.

The trace format is organized hierarchically as follows:
Platform -> Node -> Component -> Event Trace
.

INSERT picture of schema.

We summary the meaning of each table below. Table names are shown in bold.

A '''platform''' (bold) contains a set of nodes. Examples of a platform include SETI@home, desktops at Microsoft.
A node contains a set of components, which is a software module or hardware resource of the node. Each node can have several components (e.g. CPU speed, availability memory, client availability), each of which has a corresponding trace.
A component describes attributes of a software module or hardware resource of a node.
component_perf is the component performance, as measured through benchmarks for example.
A creator is the person responsible for the trace data set. This table stores details about citations and copyright.
An event_trace is the trace of an event, with all of corresponding timing information
event_state is the state corresponding to an event_trace. For example, for CPU availability, the event_state could be the idleness of the CPU. For host availability, it could be the monitoring information associated with the event.





A description of the table attributes appears below.
July 10, 2009, at 07:32 PM by 129.88.69.207 -
Added line 3:
I just add some thing

Page Actions

Recent Changes

Group & Page

Back Links