Re: appsrc/appsink API vs Signals
Eslam Ahmed via gstreamer-devel <[email protected]>
| Newsgroups | gmane.comp.video.gstreamer.devel |
|---|---|
| Message-ID | <CAHhP+STE-h766z0ooXPvPo2CUKD_vsUPhP6a02FVeWNfAS7bHg@mail.gmail.com> |
Noted, Will give it a try on a large scale! Best Regards, Eslam On Tue, Jun 6, 2023 at 9:11 AM Sebastian Dröge <[email protected]> wrote: > On Mon, 2023-06-05 at 09:27 -0400, Nicolas Dufresne via gstreamer-devel > wrote: > > Le dimanche 04 juin 2023 à 21:29 +0300, Eslam Ahmed via gstreamer-devel a > écrit : > > > I was wondering if there is a performance difference between using > appsrc/appsink via their own API (by linking gstreamer-app) or through > signals, which is more performant in large volumes? > > > There shouldn't be much difference. In all cases, the data is placed into > the appsrc/sink internal queue (unless when the queue is full were the > signal get blocked. Performance wise, there is no difference. > > > Performance of GObject signals is actually quite bad. That's also why you > have to opt-in via a property to get the signals emitted at all. > Ideally you would use the proper API instead of the signals if performance > is important. The signals were only provided for compatibility with > bindings. > > -- > > Sebastian Dröge, Centricular Ltd · https://www.centricular.com >