Arcs Archive background database process and performance impacts

Summary:

Addition to the question posted here: ARCS Archive and purge implementation questions on batch size, unarchive and epmautomate — Cloud Customer Connect (oracle.com).

We wanted to get some understanding about the background process of archive. This would help us make decision on business process and deciding the frequency of archive.

• When we archive, do the transactions move to a different database table internally or they remain in same tables until purge. Reason being we can archive more frequently and purge once every month or few weeks.

It would be also great to understand the impact of archive on performance like: