Although file upload improved with Mattermost 5.0, multiple big upload files can still crash Mattermost and I would like to know, if there’s anything to do about it
Steps to reproduce
- Upload two or three file attachments (50 - 100 MB) simultanously
- Best case scenario: Server is very slow for a couple of minutes, but uploads work
- Worst case scenario: Server crashes, uploads fail, client sometimes get an 502-error (as mattermost service is down and has to be restarted).
As I cannot coordinate or control our team user’s upload behaviour, I’d like to see, that Mattermost server would be able to “pipeline” bigger and simultanous file uploads more save and efficient. I also “played” around with Nginx proxy settings, but nothing worked so far. If there’s any other configuration tipp, please let me know.
Our Mattermost installation (5.4.0) is hosted on a
- AWS t2.micro instance
- with 1 GB RAM,
- 1 vCPU,
- Nginx as proxy, SSL enabled
- 1,7 GB additional SWAP are allocated.
- Current max file upload size: 100 MB.
- Files are saved on Amazon S3.
For our Team (a podcast project) it’s crucial to be able to handle 50 - 100 MB Audio-Files from time to time in Mattermost. But bigger uploads crashed Mattermost in the past. With ver 5.0 we hoped for an improvement (Release note: * Improved file upload API to stream files instead of loading them entirely into memory.) And usually big file uploads work. But: When multiple bigger files are uploaded simultanously, the Mattermost app still crashes.