Hey, look! I found a way to reduce the number of network requests we make. :) This makes the static cache loader more aggressive, and persists it for the entire life of the PHP process, regardless of how often Composer decides to reset itself internally.
Testing with php-tuf/drupal-project doesn't show a major performance difference, but this definitely reduces the amount of network-bound I/O, which is certainly good. You can tell by comparing the logs -- testing against this branch, you'll see far fewer requests for TUF metadata that return a 304 response code.
Hey, look! I found a way to reduce the number of network requests we make. :) This makes the static cache loader more aggressive, and persists it for the entire life of the PHP process, regardless of how often Composer decides to reset itself internally.
Testing with
php-tuf/drupal-project
doesn't show a major performance difference, but this definitely reduces the amount of network-bound I/O, which is certainly good. You can tell by comparing the logs -- testing against this branch, you'll see far fewer requests for TUF metadata that return a304
response code.