Answers.Body: <p>I am not sure what exactly the limitation is; let assume you don't want using disk I/O; how about ramdisk? <a href="https://linuxhint.com/ramdisk_ubuntu_1804/" rel="nofollow noreferrer">The link</a> tells you how</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-09-05T02:31:24.873Z
Answers.Text: Awesome, thanks.
Answers.UserDisplayName: user33276346
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-09-05T01:17:21.527Z
Answers.LastActivityDate: 2020-09-05T01:17:21.527Z
Answers.UserDisplayName: xer-rex
Body: <p>We are streaming a video using a 30 instances of docker containers hosted on Azure each instance running FFmpeg. The problem is that Azure limits the reads/writes that a container can do. Is there a way to modify the command to reduce the reads/writes needed to stream?</p>
  <pre><code>ffmpeg -re -i file.mp4 -c copy -f flv rtmps://streamingSite.com/live/x4t
  </code></pre>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-09-02T15:35:19.280Z
Comments.Text: No, that command will read the file only once, and never write anything.
Comments.UserDisplayName: SlimSCSI
Tags: <ffmpeg><encoding><streaming><live>
Title: Stream video using FFmpeg with minimum writes reads to disk
UserDisplayName: user33276346
ThreadText: # Stream video using FFmpeg with minimum writes reads to disk
  
  (Asked by: username_0 on 2020-09-02)
  
  We are streaming a video using a 30 instances of docker containers hosted on Azure each instance running FFmpeg. The problem is that Azure limits the reads/writes that a container can do. Is there a way to modify the command to reduce the reads/writes needed to stream?
  
  ```
  ffmpeg -re -i file.mp4 -c copy -f flv rtmps://streamingSite.com/live/x4t
  
  ```
  
  **Tags:** ffmpeg, encoding, streaming, live
  
  > **Comments:**
  > **username_1**: No, that command will read the file only once, and never write anything.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2020-09-05. Score: 0 | Accepted answer
  
  I am not sure what exactly the limitation is; let assume you don't want using disk I/O; how about ramdisk? [The link](https://linuxhint.com/ramdisk_ubuntu_1804/) tells you how
  
  > **Comments:**
  > **username_0**: Awesome, thanks.  
  
  ---
  
  