How to best manage FCC application size with the 3 constant currency translation scenarios

Summary:

In addition to actual scenario, the FCC application has 3 additional constant currency translation scenarios as below for reporting requirements

Are there any best practices to handle constant currency reporting in FCC to ensure we do not multiply the application size as well?

Content (required):

We are using a OOB Copy Data feature to copy data from Actuals to other scenarios every period (which works at all level 0 members) and also copy the relevant rates to the other scenarios which are then used for translation based on the specific rates needed. The functionality works fine for constant currency translation reporting however copying the actuals data at all level 0 members to 3 additional scenarios really multiplies the data base size and we are adding up to almost 5 GB to application size every period. Right now the application size is close to 150 GB