Runtime (FI-SL)
Storage Requirements
To estimate the amount of memory needed to archive summary and line item records, use the following guidelines:
|
1 Summary Record |
1 Line Item |
1 Plan Line Item |
|
|
Estimated amount of memory required in database in bytes |
800 |
300 |
800 |
The data is compressed during archiving. The compression factor depends on the data record length and content. A data record containing lots of empty fields is compressed to a smaller size than a record that is completely filled.
Database Storage Requirements when Archiving Plan Line Items
|
500 Plan Line Items |
5000 Plan Line Items |
|
|
Before archiving |
0.4 MB |
4 MB |
|
After archiving Thereof: Storage requirement for header data information Storage requirement for remaining data |
0.91 MB
0.89 MB
0.02 MB |
1.10 MB
0.89 MB
0.21 MB |
The 0.91MB of memory space required in the database after archiving 500 plan line items is made up of 0.89MB for the header data and 0.02MB for the remaining data after compression. The storage requirement for the header data information after archiving 5000 plan line items is the same as for the archiving of 500 plan line items.
The storage requirement for header data information per file depends on the number of FI-SL tables and their record lengths. Regard the data in the example as a guideline for the possible scale of the data.
Life
The time needed to run the archiving program depends on the number of records you want to archive and the system load and performance.
On average, the write program processes 1-2 million records per hour. On average, the deletion program processes 1 million records per hour. The values are guidelines. For precise information about runtimes and storage requirements for the archive file, see the test run for the write or deletion programs.