Q: Eric made the comment that it's a negative that the current ffmpeg integration wastes disk space by writing segments to disk. I wanted to open a conversation about this.
- Is it really a negative? Do we need segments to be temporarily remembered prior to the claim/verify loop in our protocol because we need to provide evidence of them later in the verify() transaction? I suppose we could instead just write metadata to disk, such as the hashes/signature that encompass the transcode receipt https://github.com/livepeer/wiki/blob/a117e9590efe4e7c9d986b2579c5ca02b11c54da/SPEC.md#transcode-receipt
- Also, we have the out of memory issue on the livepeer node because we're currently storing references to the data segments themselves within data structures, and never freeing these references. livepeer/go-livepeer#227. Should we instead be just storing references to the segments in memory, and writing the segments to disk? Or use some sliding buffer which caches a few segments in memory fo