Skip to content
English
Go to qameta.io
  • There are no suggestions because the search field is empty.

Storage and database cleanup

    Storage and database cleanup and maintenance

    Why is it important?

    Allure TestOps collects all your test results data in the database and in the artefacts storage.

    Theoretically you can store infinite data amounts to see how is wass going 1-2-3-N years ago.

    In reality – alas! – the more data you store in the database and in the storage, the more money it costs you and the less is the database performance – even if you don't retreive the data for tests you've executed 3 years ago, this information stored in the database slows down the select requests for the data you added just now. 🫥

    Historical Launches data

    What do we store in the database:
    • metadata for each test result
    • metadata for each launch
    • scenario data
    • fixtures data
    • links to the artefacts on S3

    Built-in Cleanup procedures deletes artefacts and related records in the database

    see details here - fixtures artefacts from S3 and their file references from the database - test results attachments from S3 and their file references from the database - tests results scenarios from the database and all their references from the database

    What historical data is not deleted

    Launches data

    - launches metadata from the database - each test result metadata

    The tool needs to be used with caution as the deletion of a launch is a heavy operation against the database which during the high load times could dramatically degrade the performance even to buzz state.


    Deleted data

    The data you store in the DB contains records with the historical data, data related to the paths to the files etc.  This all data is being deleted by Allure TestOps from time to time.  not deleted vacuum Options to be used for VACUUM and frequency of the procedure need to be decided by your personnel responsible for the databases maintenance considering the peculiarities of VACUUM procedure described in the article mentioned above (exclusive locks etc.). After the historical data or the artefacts are deleted, you need to run VACUUM to reclaim the wasted space on the database storage.