> For the complete documentation index, see [llms.txt](https://competitions.gitbook.io/competition-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://competitions.gitbook.io/competition-docs/performance/archiver.md).

# Archiver

{% hint style="warning" %}
Archiver is an add-on plugin specifically made for high volume or older sites
{% endhint %}

### Why do I need this feature?

As you sell millons of tickets overtime your database becomes bloated with data. Tickets sold a year ago are not needed anymore so there is no need to have them in your active database which is used everyday when someone places an order.

This is not only for older sites though as recently more competition sites are doing penny prizes. Penny prizes will speed up the process of a bloated database, you'll have more orders coming in and those orders will typically have hundreds of tickets in them, so if you typically do penny prizes with max tickets over 100,000 you can easily have millions of data in a few months.

### How do I know if I need it?

If your website has become slower and slower overtime and the orders take longer and longer to fufill you most likely need it. Any complaints from customers about a slow ordering system would be a clue to a bloated database - If you also do a lot of penny prizes then most likely you need this feature if you've been running them for a while.

{% hint style="success" %}
Customers will still see their wins on their My Account page
{% endhint %}

### How does it work?

Depending on your configuration in non-peak hours (8am to 1pm) this feature will automatically turn on and look for old data that needs to be moved out of the live database and into a dormant database that can be tapped into if neccessary. You can choose between archiving orders and tickets or both aswell as setting the timescale to archive.

{% hint style="info" %}
We will normally configure this for you but for example purposes please see below
{% endhint %}

<figure><img src="/files/hrF5MeiAmKVsNwMUZjkL" alt=""><figcaption></figcaption></figure>

These options decide when the automatic archiver will archive data. If you click 12 months then anything older than 12 months goes into the dormant database.

The dormant database can be tapped into in a table which looks up the archived data.

When you click View you will see all the order details as normally, this allows you to look into what tickets they bought, billing information and all your usual information in the rare case you need to lookup an old order.

{% hint style="warning" %}
This plugin is constantly evolving and we will try to update this page with any new features
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://competitions.gitbook.io/competition-docs/performance/archiver.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.