Hi,

As I'm migrating v1.4 stuff to v2.0, it's expected that I often use liquidsoap -h xx to check on new syntax... And it's quite slow, on my machine and my test env. I use the .deb provided by the ci @ github.

time liquidsoap --version
Liquidsoap 2.0.0
Copyright (c) 2003-2021 Savonet team
Liquidsoap is open-source software, released under GNU General Public License.
See <http://liquidsoap.info> for more information.
liquidsoap --version  1,13s user 0,06s system 99% cpu 1,193 total

$ time liquidsoap -h print
[...]
liquidsoap -h print  1,81s user 0,05s system 49% cpu 3,755 total


So I'm guessing there is some runtime evaluation of what is dynamically available, and that the docker build doesn't suffer from it, because:


$ time docker run -it savonet/liquidsoap:v2.0.0 --version
Liquidsoap 2.0.0
Copyright (c) 2003-2021 Savonet team
Liquidsoap is open-source software, released under GNU General Public License.
See <http://liquidsoap.info> for more information.
docker run -it savonet/liquidsoap:v2.0.0 --version 0,02s user 0,03s system 3% cpu 1,455 total

$ time docker run -it savonet/liquidsoap:v2.0.0 -h print
[...]
docker run -it savonet/liquidsoap:v2.0.0 -h print 0,02s user 0,04s system 3% cpu 1,969 total

So, before I dig into this (or switch fully to docker for that env, but I'd rather not), is there obvious runtime discovery behavior that can be shut off through settings?

Cheers,
Gilou


_______________________________________________
Savonet-users mailing list
Savonet-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/savonet-users

Reply via email to