>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3564027. --> Reported by: [phenaproxima](https://www.drupal.org/user/205645) Related to !30 >>> <p>The performance test for Byte is interfering with development. It's flaky, it needs updating all the time, it's extremely slow (ironic!) and it is of somewhat uncertain benefit -- after all, end users don't care about things like how many cache tag queries are being done, or how many bytes of CSS are being loaded, so long as they experience a quick load time.</p> <p>I don't think we should remove the test outright, or any of the infrastructure for it, but we need to recognize the reality that it's an albatross around our neck, and we're fighting it more often than we are getting any help from it. We are not doing forensics on performance test metrics, or any continuous analysis. We are not investigating why their numbers fluctuate; we just fix the test and move on. It's not delivering the hoped-for benefits.</p> <p>So let's change our CI setup so that the performance test a) runs in its own job, and b) is manually triggered, never automatically run.</p>