Does composer load the site on production?

Question

Composer

It is interesting to know if composer loads as an overhead on the server. When choosing a hosting, we have cms at hand and everything, and on vds you can have all sorts of composes, mailers and whatever you want. I read that the composer must be installed if the framework is installed, but you can install it without the composer. The composer does auto-loading, and here is the question, does it do it asynchronously and this does not particularly affect the site, or does it generate classes every time a request is made to the server, and thereby loads it. Did I wind it up myself or is there such a note?

Answer 1

You correctly wrote that in an amicable way, you need to work with Composer on a local machine.
But, if you drive it on a combat vehicle, be sure to keep in mind that Composer uses a completely obscene amount of RAM (and the author answers questions about this, in fact, with mockery).
For example, to install Drupal 8 or update one installed module, you barely have enough gigabytes . Something more serious may require more.
So I would put in RAM consumption of about 1-1.5 GB when Composer is running. The load on the processor will also not be zero, but it is still much more tolerable.

Answer 2

composer works when you run it.
If you write in the console

composer create-project symfony/skeleton my-project

- composer will execute your command for some time.
If you don't give any commands, it does nothing.

Answer 3

The composer does not load the server. And it does not do any "autoloading".
It shouldn't be in production. As well as version control systems.
Only the code should be released to production.