Issue
In order to always achieve optimum optimal project performance in the project while keeping operating costs low, it is important to pay attention to which consider what data is imported into test.guide in the first place. Unnecessary data that is not required needed in test.guide only costs performance and storage space, and therefore money.
Since 80% of the data are is usually attributes and constants, the focus is on optimizing them. Methods for optimizing data handling are presented below.
Solution
| Table of Contents | ||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Quick analysis of the current stored constants and attributes
...
| Info |
|---|
The easiest way is to manage the ATX generator settings centrally via test.guide, then the adjustments can be set directly made for the entire project: Project settings > ecu.test |
...
If you have no influence on the ATX export, e.g. because it is provided by other teams, test.guide offers the option since version 1.171.0 the possibility to define which attributes or constants are recorded in test.guide via the upload rules (Project settings > Upload rules) which attributes or constants are recorded in test.guide. All others are will be discarded.
...
Retroactively remove unused attributes and constants
If all upload settings have been made and you now realize during the analysis that there are many unused attributes/constants in your project that , you can be permanently deleted, this is possible permanently delete them using the recycle bin function (Project settings > Recycle bin) function.
...
If you discover within a few days after deletion that certain attributes or constants are still missing for filtering/analysis are still missing, these they can be restored as long as the recycle bin has not yet been emptied.
...
| Note |
|---|
The attributes and constants are also permanently removed from locked releases! |
| Info |
|---|
In order to prevent mass deletions from affecting ongoing operations, only one deletion action can be carried out in the project at a time. |
Define cleanup rules
If, for For example, if the current test runs / integrations / trials have been completed and the important results are locked as a release, it is beneficial to directly define a cleanup rule that automatically removes all data from test.guide that is no longer requiredneeded.
...
| Info |
|---|
This has the advantage The advantage of this is that only the results that are relevant to the for delivery remain available via the locked releases, and no unnecessary data is kept in the project for longer. |