We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Currently the spawned ffmpeg process by the PeerTube runner writes a lot to the physical storage backed ~/.cache directory.
ffmpeg
~/.cache
This wears out the hardware unnecessarily.
On systems with sufficient (>= 16GB) free available system memory, for the PeerTube runner to use the XDG provided tmp directory instead.
This'd lessen the wear of physical storage during transcoding.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the problem to be solved
Currently the spawned
ffmpeg
process by the PeerTube runner writes a lot to the physical storage backed~/.cache
directory.This wears out the hardware unnecessarily.
Describe the solution you would like
On systems with sufficient (>= 16GB) free available system memory, for the PeerTube runner to use the XDG provided tmp directory instead.
This'd lessen the wear of physical storage during transcoding.
The text was updated successfully, but these errors were encountered: