Details
-
Type: extRequest
-
Status: Closed
-
Priority: Major
-
Resolution: Done
-
Fix Version/s: 2021
-
Component/s: FIWARE-TECH-HELP
-
Labels:None
-
HD-Chapter:Cloud
-
HD-Enabler:Object Storage
Description
Hello,
We are verifying across several uploaded files of varying sizes and types that the size of the stored file vs the uploaded one suffers an increase in size of about 1,27 times (a file with an original size of 375MB results in a stored file with 477MB).
For small files this is not a big issue but taking into account that large data files could be uploaded following this size increase ratio, a file with an original size of 5GB would result in 5,8GB, which is almost 1GB of increased size.
This results in a poor utilisation of the cloud storage space and there is space for optimisation.
Browser: Safari 8.0
OS: Mac OS X 10.10
Hello. To confirm - the Web Portal displays a larger file size than the original because the Web Portal has encoded the original file using Base64 encoding, before it passes it to the Object Storage GE. Base64 encoding increases a file size - see previous comment in thread.
Binary files can also be sent directly to the Object Storage GE - they will be stored with the original size. However, as mentioned previously several copies of the content will be stored on the back-end for redundancy.
I believe this ticket can be closed. Another possibility is to investigate if the portal can be re-engineered to avoid the need to Base64 encode. This may not be trivial depending on the support provided by the underlying technologies the portal uses.
Thank you - John