When we try to install/update some stuff with composer, anyway we put -1 memory (or +1000) it still not working, to solve this we can create a swap file.
Here is the trick:
mkdir -p /var/_swap_
#Here, 1M * 2000 ~= 2GB of swap memory
dd if=/dev/zero of=swapfile bs=1M count=2000
swapon swapfile chmod 600 swapfile
echo "/var/_swap_/swapfile none swap sw 0 0" >> /etc/fstab
Using a fresh install of drupal in simpletest.me, let's do these steps:
This display uses render entity with Teaser view mod. This mod has body and image fields. Path is /article-render
This display uses views fields, we have to set up field by field, in this case, we add the same fields that teaser view mod has.
Now let's create some articles with Devel Generate Content. yoursite/admin/config/development/generate/content", select article and do generate.
Now we have the content and two view pages, lets check with web-profiler which of those displays is more efficient. Our check is always after cleaning the caches, because the cache reduces the loading time to same.
Without caching the page, the views fields is more efficient because it is doing less queries than render content display. But in a real world, who set up pages without caching?
PS Build pages or blocks of content like list of teasers with view mods give us the opportunity to use the powerful of twig and set up custom html for this pieces of content. Instead, with views field we should manipulate the preprocess of views elements.