Are you using a Puppet Server container from https://hub.docker.com/r/puppet/puppetserver? If not, it'd be helpful to know what your Dockerfile is doing.
I'm not sure there's been a lot of tuning done for the Puppet Server container we publish. The Puppet Server process itself usually starts in 15-30s (last time I looked at it), and that's mostly compiling and initializing Clojure library code. We periodically look at ways to improve this (GraalVM should be great once it's complete enough, but Puppet Server might need architectural changes to take advantage of it), but I'm not aware of any simple options. However 2 minutes sounds like a long time, so there are likely other things happening that could be sped up. If I start an instance locally, I see it taking about 40 seconds from invoking 'docker run' to being ready to handle requests: 10-15s in startup scripts, about 10s for the Clojure interpreter to start up, and 15-20s starting various services. There aren't simple toggles to improve any of those that I'm aware of. On Mon, May 11, 2020 at 7:10 AM David Moreno García <david.mo...@gmail.com> wrote: > Hello, > > I'm using Puppet Server (Open Source 5.3.6) in a container environment > (Kubernetes 1.18). In this deployment, I'm scaling the pool of containers > taking into account the load (number of catalog compilations). I create new > containers when the load is high and I remove containers when they are not > needed. > > My problem with this approach is that the process is not as fast as I > would like. The Puppet Server, with 2 instances, takes around 2 minutes to > be ready. On top of that, the first compilation is slower. This means that > if I need a new container to process an incoming request, I will have to > wait a minimum of 2 minutes plus the extra time required to compile that > first catalog. > > Here I want to focus in the startup time for the Puppet Server. Would > there be any option to improve this time? > > I've been taking a look into CRIU <https://criu.org/Main_Page>, which is > not really an option. > > Any idea is welcome. Also, as this question is a bit abstract as right > now, feel free to ask for any specific detail about the deployment. > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-dev+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-dev/b726a428-5b76-42f7-90be-9763348b6626%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-dev/b726a428-5b76-42f7-90be-9763348b6626%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/CABy1mMKnzTeGmG-k_CXqdBQVQL27jG9AxZSMHDqfBOetY9nDiQ%40mail.gmail.com.
