Problem/Motivation

The routing subsystem does a couple of stuff:

From an incoming request, it determines the active controller, which is used to render the "current page".
On that page, there might be links to other elements of the page, so it generates URLs, to those places.

On top of that people enter in PATHs in menu links etc. for which we have to determine the routing information as well, but potentially
multiple times per request.

Each of those 3 usecases have dedicated issues to speed things up:

  1. #2406117: potentially cache parts of routing #2084675: Quering the database for router items is slow (access checking)
  2. #1965074: Add cache wrapper to the UrlGenerator #2074297: Optimize the code in doGenerate() in the UrlGenerator to take advantage of Drupal path restrictions.
  3. #2370651: Make (routing by path) cacheable

Proposed resolution

Remaining tasks

User interface changes

API changes

Comments

fabianx’s picture

Priority: Normal » Major

Thanks for opening the meta!

fabianx’s picture

webchick’s picture

Issue tags: +D8 Accelerate Dev Days

Tagging.

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Crell’s picture

Status: Active » Fixed

I just closed the last 2 child issues, so let's call this done. :-)

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.