On 08/29/2013 11:51 PM, Martin Storsjö wrote:
Hi,
On Thu, 29 Aug 2013, aviad rozenhek wrote:
the question is, why is libav using unbuffered I/O, and does moving to
fopen make sense?
Because libav already has got a buffering layer of its own, AVIOContext,
which provides buffering on top of whichever unbuffered API is used
below (file descriptors, sockets, etc). If this buffering doesn't work
properly for your case, you're probably hitting some corner case in it
where the buffering doesn't help as much as it should (or the input file
is structured in a way that forces the IO layer to seek a lot).
Instead of adding buffering at yet another layer it would make more
sense to try to figure out why the existing buffering doesn't help in
your particular case, and if there's something that can be done about it.
as he said:
I'm seeing slow I/O performance in libav while muxing mp4 files.
is there any buffering layer in case of muxing MP4? I'd guess there is
none, no?
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel
