Project Name: VideoCutTool
Tool: videocuttool.wmflabs.org
Curent quota got exhausted:
 |  |
Type of quota increase requested:
| Type | Current Quota | Requested Quota |
| RAM | 16 GB | 48 GB |
| Cores | 8 | 24 |
| Storage | 160 GB | 320 GB |
Detailed usage of this quota:
| Instance | VCPUs | Disk | RAM |
| video-cut-tool (front-end and back-end) | 2 | 60 GB | 4GB |
| video-cut-tool-worker | 12 | 140 GB | 24 GB |
| video-cut-tool-worker-1 | 10 | 120 GB | 20 GB |
Reason:
Nowadays we worked a lot and improved the functionality, usability, and stability of the tool, We are sooner going to release the later version with much more abilities. VideoCutTool uses ffmpeg for its video encodings and all these computations require a good amount of RAM, Cores to perform faster and serve better. Recently we have launched 0.4 version of the tool and took the user's feedback, We got to know we need to work on the performance (Also: T276002), So we revamped the back-end and service workers logic and then requesting this quota to make the tool perform better and become stable.
After this request approval, we are also planning to propose moving this tool to the commons sidebar as default similar to CropTool as currently it's available as a gadget and users have to enable it's from their settings.
Resources:
- More cores and ram makes the video computations faster with ffmpeg: https://qr.ae/pG7Dy7
- Testing results also say that more Cores and more RAM makes the computation faster with ffmpeg: https://write.corbpie.com/ffmpeg-x264-encoding-more-cores-or-faster-cores/