>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3202601. --> Reported by: [adamzimmermann](https://www.drupal.org/user/1152646) >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>This module looks really cool, but I'm struggling to understand the "why" behind when I would use it. Adding something about why it was developed or under what use cases someone might want to use it might help adoption. I'm happy to help draft this content if someone can explain it to me! Thank you in advance for any insight.</p> <p>Also, selfishly I'm trying to understand if it would fix my issue. </p> <p>I'm hoping your answer to my questions above can shed light on an answer to my underlying question:</p> <p>I'm working on a site with ~13,000 menu items and running <code>drush cr</code> takes several minutes and causes us to exceed our PHP memory limit in production. We have temporarily disabled the route rebuild port of <code>drush cr</code>, which has many unwanted/bad side-effects. I'm wondering if the use of this module as a sort of "cache" of our menu items would allow us to iteratively rebuild menu item access in the background.</p> <p>i.e. run this at our leisure.<br> <code>\Drupal::service(&lsquo;router.rebuild&rsquo;)-&gt;rebuild()</code></p> <h4 id="summary-steps-reproduce">Steps to reproduce</h4> <p>N/A</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>Add "why" documentation.</p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <p>Write documentation and update project page.</p> <h3 id="summary-ui-changes">User interface changes</h3> <p>N/A</p> <h3 id="summary-api-changes">API changes</h3> <p>N/A</p> <h3 id="summary-data-model-changes">Data model changes</h3> <p>N/A</p> <h3 id="additional-context">Additional Context</h3> <p>I found this module by searching to see if anyone had explored adding SQL indexes to the <code>menu_link_content</code> tables. </p>