[x264-devel] Optimizing x264 for lowest memory usage
Yakov Sudeikin
yakovs at setplex.com
Tue Mar 8 18:42:29 CET 2016
I am using x264 with GStreamer.
advice to use -Os is not helpful. I am talking about 4GB ram used by x264
in encoding. Os can save kilobytes if you were lucky.
On Tue, Mar 8, 2016 at 11:34 PM, Vittorio Giovara <
vittorio.giovara at gmail.com> wrote:
> On Mon, Mar 7, 2016 at 2:43 PM, John Pham <john.pham at gmail.com> wrote:
> > -Os is just for compiling option - is this a run time issue ?
>
> -Os is a compile time option that produces smaller code, making cache
> and memory constrained environment very happy. Given no information
> was provided about how x264 is called or where x264 is executed, this
> is the best option available.
> --
> Vittorio
> _______________________________________________
> x264-devel mailing list
> x264-devel at videolan.org
> https://mailman.videolan.org/listinfo/x264-devel
>
On Tue, Mar 8, 2016 at 11:34 PM, Vittorio Giovara <
vittorio.giovara at gmail.com> wrote:
> On Mon, Mar 7, 2016 at 2:43 PM, John Pham <john.pham at gmail.com> wrote:
> > -Os is just for compiling option - is this a run time issue ?
>
> -Os is a compile time option that produces smaller code, making cache
> and memory constrained environment very happy. Given no information
> was provided about how x264 is called or where x264 is executed, this
> is the best option available.
> --
> Vittorio
> _______________________________________________
> x264-devel mailing list
> x264-devel at videolan.org
> https://mailman.videolan.org/listinfo/x264-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.videolan.org/pipermail/x264-devel/attachments/20160309/e1ef386c/attachment.html>
More information about the x264-devel
mailing list