Allow zip files larger than 50MB or a way to upload larger files

[eperez84]

Is your feature request related to a problem? Please describe.
No

Describe the feature you'd like
Had to run a load test which required uploading large video and image files. Unfortunately due to the 50mb file size cap, we had to reduce the number of images and videos that were used. One (or both!) of the following would be nice to have:

• Bump up the maximum size of the zip file - 100, 200, or 300mb?
• Allow us to upload files to S3 or some other working directory which we can reference in the *.jmx script. When testing a workaround, I noticed that the script was trying to pull the non-existent video file from /bzt-configs/ which is somewhere inside the container and not accessible.

Additional context
N/A

[owen-brady]

Hey @eperez84 - thanks for reaching out!

Could you elaborate a bit on the use case and upper limit you'd like to have? I'm assuming there's a need to test media uploads?

We can increase the file size can - we just need to be careful with overall memory utilization for the Fargate tasks to make sure they don't run out of memory and crash.

We've discussed adding parameters to change the task definition for adjusting vCPU and memory. That might be relevant for this enhancement.

We will review the request and provide an update once we have more information.

---

If you need a fast alternative and have access to the S3 bucket

You could upload directly to S3 and see how it goes.

1. Find the ScenariosBucket name either in the CloudFormation stack output or from the "Raw Test Results" link in the DLT UI
2. Grab the test scenario ID
3. Navigate to {MY_BUCKET_NAME}/public/test-scenarios/jmeter/
4. Replace {TEST_ID_TO_REPLACE}.zip with your larger zip using the same file name

[eperez84]

@owen-brady Thanks for the prompt response. Correct, we had to run a load test which necessitated the use of large media files. The ideal payload file size range for upload was between 230-600MB and we had to trim this down to about 41MB. I completely understand your concern with regards to memory utilization and stability. This is not something I had considered.

Your workaround seems like a viable option and I will give it a shot today. Appreciate it!

[jordanst3wart]

200MB would be enough for me, with 170MB being something related to a headless web driver