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 "TPTP Miscellaneous"
(→TPTP Model Scalability) |
|||
| Line 11: | Line 11: | ||
== [[Build to Manage]] == | == [[Build to Manage]] == | ||
Here is some information about [[Build to Manage]] | Here is some information about [[Build to Manage]] | ||
| + | |||
| + | == TPTP Model == | ||
| + | TPTP Model is covered in this page [[TPTPModel | TPTPModel]]. | ||
| + | |||
== TPTP Model Scalability == | == TPTP Model Scalability == | ||
===[[TPTP DMS]]=== | ===[[TPTP DMS]]=== | ||
| + | |||
In TPTP 4.4 there are two effort underway to improve the scalability of the persistence framework. The first is a longer term effort being done jointly with the COSMOS project to define a common set of data services for the kinds of data both projects deal with. This includes log, statistical and trace data as well as network topologies among other things. TPTP collects and provides access to this type of data in support of problem determination tasks done in a development an test environment. This is primarily done through an Eclipse based user interaction. COSMOS target larger scale execution environments than development and unit test, and also provides the prime user experience via a browser. For more information on the TPTP aspects of this effort follow this [[TPTP DMS | link]]. To read about COSMOS follow this [http://www.eclipse.org/cosmos link]. | In TPTP 4.4 there are two effort underway to improve the scalability of the persistence framework. The first is a longer term effort being done jointly with the COSMOS project to define a common set of data services for the kinds of data both projects deal with. This includes log, statistical and trace data as well as network topologies among other things. TPTP collects and provides access to this type of data in support of problem determination tasks done in a development an test environment. This is primarily done through an Eclipse based user interaction. COSMOS target larger scale execution environments than development and unit test, and also provides the prime user experience via a browser. For more information on the TPTP aspects of this effort follow this [[TPTP DMS | link]]. To read about COSMOS follow this [http://www.eclipse.org/cosmos link]. | ||
| + | |||
| + | The original TPTP DMS page can be found here [[TPTP_data_persistence_layer | TPTP data persistence layer]], which also contains information about the infrastracture used in the COSMOS EclipseCon 2007 demo. | ||
===[[TPTP Test Log Scalability]]=== | ===[[TPTP Test Log Scalability]]=== | ||
The second effort is more near term focused but has similar scalability objectives. Basically by using the concepts implemented in the Log Analyzer "large log" support, we will provide an optional RDB storage system for test execution logs. This will optionally load all the data directly into a relational database, and the UI will only query out the needed information. The intent is to remove the current limitation of the Test perspective which holds all data in memory and thus limits the amount of information that can be processed. For more information follow this [[TPTP Test Log Scalability | link]]. | The second effort is more near term focused but has similar scalability objectives. Basically by using the concepts implemented in the Log Analyzer "large log" support, we will provide an optional RDB storage system for test execution logs. This will optionally load all the data directly into a relational database, and the UI will only query out the needed information. The intent is to remove the current limitation of the Test perspective which holds all data in memory and thus limits the amount of information that can be processed. For more information follow this [[TPTP Test Log Scalability | link]]. | ||
Revision as of 14:26, 4 April 2007
TPTP main page > TPTP Wiki home >
Contents
How to "Smoke Test" the new technology agent controller
Different versions of TPTP from a build perspective
Performance comparisons of the 4.3 "new tech AC" vs. "the RAC" vs. "the IAC"
Build to Manage
Here is some information about Build to Manage
TPTP Model
TPTP Model is covered in this page TPTPModel.
TPTP Model Scalability
TPTP DMS
In TPTP 4.4 there are two effort underway to improve the scalability of the persistence framework. The first is a longer term effort being done jointly with the COSMOS project to define a common set of data services for the kinds of data both projects deal with. This includes log, statistical and trace data as well as network topologies among other things. TPTP collects and provides access to this type of data in support of problem determination tasks done in a development an test environment. This is primarily done through an Eclipse based user interaction. COSMOS target larger scale execution environments than development and unit test, and also provides the prime user experience via a browser. For more information on the TPTP aspects of this effort follow this link. To read about COSMOS follow this link.
The original TPTP DMS page can be found here TPTP data persistence layer, which also contains information about the infrastracture used in the COSMOS EclipseCon 2007 demo.
TPTP Test Log Scalability
The second effort is more near term focused but has similar scalability objectives. Basically by using the concepts implemented in the Log Analyzer "large log" support, we will provide an optional RDB storage system for test execution logs. This will optionally load all the data directly into a relational database, and the UI will only query out the needed information. The intent is to remove the current limitation of the Test perspective which holds all data in memory and thus limits the amount of information that can be processed. For more information follow this link.