What is the difference between the usual caching mechanism for components and the Bitrix composite?

Question

1C-Bitrix

Bitrix components are equipped with the ability to cache the result of their work and give users html from the cache. Why additionally transfer components to composite mode and make cache / non-cache markup inside them? And will it really speed up the page speed by 100 times?

Answer 1

In normal mode, the site page is assembled as a whole - the general template and individual components are executed, which may or may not cache their templates.
Composite site - a technology that allows you to cache the entire page with all the components. On the first hit, we generate it and save the html to the memcache. If you hit the same page again with the same parameters, it will be served directly from the memcache (if everything is set up). In this case php will not connect at all. But that's only if you don't have dynamic areas that are user-specific. For example, a shopping cart.
If it is, then the page will still be returned from the memcache, but during the loading of Bitrix js it will send an additional request to get the area with the basket.
More details - dev.1c-bitrix.ru/learning/course/?COURSE_ID=39
It strongly depends on the project. Worth a try.

Answer 2

Now there is a so-called Autocomposite. The essence of which is that you no longer need to climb the templates of the components marking them, but it is enough to indicate the mode of operation of the composite in the component parameters, on the corresponding tab.
As for acceleration, with a normally configured php cache, and correctly written templates (without logic), everything will work quickly anyway. The inclusion of a composite gives an increase, but minimal.
If the upload speed has increased 100 times, then someone has big problems with writing code and setting up Bitrix.