docs: add performance section to README

README.md

@@ -77,6 +77,25 @@ Users may still want to define a custom versions of the plugin set, or want to p
 }
 ```
 
+### Performance
+Naturally, the more packages in a monorepo, the longer it takes `semantic-release` to run against all of them. If total runtime becomes a problem, consider the following optimization:
+
+#### Reduce expensive network calls (50%+ runtime reduction)
+By default, `semantic-release`'s `verifyConditions` plugin configuration contains `@semantic-release/npm` and `@semantic-release/github`. These two plugins each make a network call to verify that credentials for the respective services are properly configured. When running in a monorepo, these verifications will be redundantly repeated for each and every package, greatly contributing to overall runtime. Optimally, we'd only want make these verification calls one time.
+
+By moving these plugins to the `verifyRelease` configuration, they will only run if `semantic-release` determines a release is to be made for a given package (at a time when the given verifications are actually relevant). Likely, most times `semantic-release` is run over a monorepo, only a small subset of all packages trigger releases.
+
+NOTE: To allow for dynamic code, this example defines the release configuration in [`.releaserc.js`](https://github.com/semantic-release/semantic-release/blob/caribou/docs/usage/configuration.md#configuration) instead of inside of `package.json`.
+
+```js
+module.exports = {
+  verifyConditions: [],
+  verifyRelease: ['@semantic-release/npm', '@semantic-release/github']
+    .map(require)
+    .map(x => x.verifyConditions),
+};
+```
+
 ### Advanced
 
 The set of `semantic-release-monorepo` plugins wrap the default `semantic-release` workflow, augmenting it to work with a monorepo.