I tried to read the description but I didn't understand what this component does. The description says:

If not checked, the bundler will not split up aggregates.

I know that the purpose of aggregation is the join files so I guess this splitting isn't de-aggregation, so what is it?

In CSS bundling option it says:

If file count is selected then each bundle will try to have a similar number of original files aggregated inside of it.

If file size is selected then each bundle will try to have a similar file size.

An answer on the question above could help me decipher what's written here as well...

  • 2
    Thanks for asking about this. Looks like I need to update the description and documentation. – mikeytown2 Dec 7 '16 at 2:13

The short answer is to take advantage of the browser cache. It can also be used to take advantage of the number of parallel connections that the browser can make.

Example: Front page has a.css and b.css; node 1 has a.css, b.css and c.css. If using one aggregate then the user going from the front page to node 1 would have to download all of the CSS again. By splitting up the aggregate in a smart manner the user will only need to download c.css

| improve this answer | |
  • Sadly, really sadly, I think I still miss how bundler works. The only thing I do think I get right in this, is that Bundler will make no change if caching is off. – user16289 Dec 8 '16 at 12:17
  • Here's google trying to explain how the browser cache works; pretty dense info. AdvAgg/Bundler doesn't work if the Aggregate and compress CSS files and Aggregate JavaScript files are unchecked on the admin/config/development/performance page. The status report page (admin/reports/status) will usually complain if something in advagg isn't working correctly. – mikeytown2 Dec 12 '16 at 22:41

Aggregated bundles can be aggregated in groups. For example, let's say there was some CSS you wanted included in the head tag and other CSS that should be included towards the bottom of your page. In this case there might be two aggregate groups.

In AdvAgg I believe the use-case you really want to look at is for JS more so than CSS. In JS you may have a "site-wide" group and a "theme" group and...

You can also have AdvAgg break up the groups by filesize or number of files being aggregated. There are some old browsers (read <= IE6) that have some issues with number of included CSS and number of CSS definitions in a single CSS file... these settings can be used to help with that.

Also, there are some HTTP2 improvements that make file aggregation less necessary for the typical use case (fewer TCP connection === better), but sometimes you would still want to aggregate in order to keep certain files together since they are functionally similar.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy