Problem/Motivation

It turns out, there is a chance that we call out to RouteProviderInterface::getRouteByName() pretty easily, and potentially hit the routes not being preloaded.
This results easily in DB query, which is absolutly not for free.

Proposed resolution

Let's discuss whether this is a problem we should care about.
If we care about it, we could store the cached entries in cache, so we don't have to hit the DB, depending on your installation.

Remaining tasks

User interface changes

API changes

Comments

fabianx’s picture

fabianx commented
Parent issue: » #2448599: [meta] Speed up routing related code

In which case does that happen?

dawehner’s picture

dawehner
Primary language German
commented

#2474055: Performance regression in contact_help() was one of those cases ... well basically when a URL is generated, #1965074: Add cache wrapper to the UrlGenerator would have solved that.

wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented

How would we know which to cache/preload?

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

Crell commented
Status: Active » Closed (won't fix)

I'mma say this isn't something to worry about, or at least there are bigger fish to fry.