50 MB file limit seems arbitrary and small

[drop-aakarsh]

Problem:
I am trying to setup a test where we use user credentials to access APIs. In order to make it secure, we want to store the credentials in a file encrypted using the aws-encryption-sdk. In the JMeter test plan, we preprocess the file and decrypt it before loading the credentials. This requires the aws-java-sdk.jar and aws-encryption-sdk.jar to be added as plugins. However, the file size of these .jar files is already beyond the allowed file size limitations.

I know this limit was previously increased from 5mb to 50mb, however, I am not sure why any such restriction on file size is required.

distributed-load-testing-on-aws/source/console/src/Components/Create/Create.js

Line 30 in f616d63

const FILE_SIZE_LIMIT = 50 * 1024 * 1024;

Describe the feature you'd like
The limit on file size seems unnecessary and it limits the scope of tests we can run using the solution.
I know this limit was previously increased from 5mb to 50mb, however, I am not sure why any such restriction is required.
I propose removing the upload file size limit as it seems arbitrary/or at least bump it up to allow installation of larger sized plugins in the uploaded zip file.

[G-Lenz]

Hi @drop-aakarsh

Thank you for pointing this out. We have added this to our backlog for further investigation.

[julian-price]

I have faced a similar problem when running Gatling tests through a modified version of the DLT. BZT supports Gatling and we use this internally for performance testing of UX. When creating an uber jar of the Gatling project in order to execute it via BZT, it exceeds the 50MB limit imposed by the DLT console.

[kamyarz-aws]

@julian-price We are working on increasing the limit. We will update you. Also since you are customizing the code you can go to create.js under Frontend component and change the value of FILE_SIZE_LIMIT.

Additionally we are accepting Pull requests if you want to share your gatling code with us.