When you run a Quality project or export a Quality project to batch, you set the following data processing options depending on your needs:
- Minimize Disk Space. This option uses less disk space by compressing the source files and intermediate output files created by the Quality processes.
- Maximize Performance. This option maximizes the performance of the Quality processes by keeping the source files and intermediate output files uncompressed.
Note: By default, the Maximize Performance option is set for both Quality projects and batch
exports.
How to Set Options
Set the data processing options when you perform the following tasks:
- Modify the details of a Quality project. You can change the option at any time, although when you do so after you run the project, you must re-run the project to activate the change.
- Configure the export of a Quality project for batch.
Deciding to minimize disk space depends on your performance needs. For example, when you compress data, less disk space is needed to run a process and store source files and intermediate output files, but the time it takes to run a process may be longer depending on the characteristics of your input data.
When you need Quality processes to run more efficiently and disk space is not a concern, then you may decide to keep the data uncompressed to maximize performance.
Guidelines
Note the following:
- Minimizing disk space in your Quality projects does not change how you view and work with data in the Control Center.
- The final output files from batch projects are never compressed.
- When you copy a project to the Project Library, no data processing settings are included. When you copy a library project into a Quality project, the library project inherits the target project's data processing setting.
- Output entities retain their data processing settings, as follows:
- If you use an output entity from a compressed project as the input to a new project, the project will inherit the entity's compressed data processing setting (Minimize Disk Space).
- When you add an output entity from a compressed project to an uncompressed project, the data processing option in the target project will be automatically set to compressed (Minimize Disk Space). Conversely, when you add an output entity from an uncompressed project to a compressed project, the data processing option in the target project will be automatically set to uncompressed (Maximize Performance).
- If you modify the data processing option in a project that contains an output entity from another project that uses a different data processing option, the other project's data processing option will also modified based on this association.
- User-Defined Processes (UDPs) work only with uncompressed input and output data. Therefore, if you minimize disk space in a Quality project that contains one or more UDPs, the output of the process preceding the UDP and the output from the UDP will be uncompressed. All other intermediate files in the project remain compressed.
- Exported compressed files cannot be opened and viewed outside of the Control Center.
- You can compress data in your project while also configuring specific processes in the project to run using pipes, further minimizing the disk space required for the process. If you use pipes when you run the entire project, you do not need to minimize disk space using data compression. For information about using pipes, see Executing a Process.
- If you use the Batch Deployment Tool (BDT) to create batch scripts, there is an optional argument (–no_data_compress) available if you need to run the BDT without compressing the source files and intermediate output files.