Problem/Motivation

In an effort to optimize how the config for this module was fetched, I implemented a separate caching for the configs. But never really did any benchmark comparisons on whether this was actually helpful. In the similar module, Bot Blocker, I recently ran such benchmarks, and found that the caching approach was actually more detrimental than just using the standard config system.

This issue is to remove that extra caching, and just use the standard Drupal configs.

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

bburg created an issue. See original summary.

dieterholvoet made their first commit to this issue’s fork.

dieterholvoet’s picture

Status: Active » Needs review