Preloading registry to avoid cpu spikes

[Yu You]

It depends on how your Docker gstreamer images were built. One option that
could possibly work is to add "RUN gst-inspect-1.0" to your Dockerfile so
that the registry would be created into the final image during the image
build phase.

Good luck.

Yu

On Tue, 7 Jun 2022 at 02:47, Guru Govindan via gstreamer-devel <
gstreamer-devel at lists.freedesktop.org> wrote:

> Hi There,
> I have a docker container that runs multiple pipelines sometimes upto 16
> Gstreamer pipelines concurrently.
> When the docker container starts there is a CPU spike increasing the load
> average which fails other services in that computer.
>
> On digging I see that the gst_init() and internally gst_update_registry()
> might be the reason behind it as it is updating the registries for the
> plugins.
>
> Since all the pipelines are more or less using the same plugins, I was
> wondering if I can copy the `registry.x86_64.bin` default into the docker
> container while building the image so that I can avoid this.
>
> Or is there any other way to reduce this?
> Please advise
> Thanks a lot!
> Regards,
> Guru
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/gstreamer-devel/attachments/20220607/bcc9bddf/attachment-0001.htm>