fix(gatsby-plugin-mdx): generate mdx once when multiple mdx fields requested #32462
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR is a performance improvement for one specific usage scenario of the MDX plugin. It addresses inefficiency in the plugin when multiple GraphQL fields are requested that require MDX processing. An example query that is affected:
In this case, the plugin starts two MDX processing tasks concurrently as shown on this chart:
This PR accounts for such a scenario and only processes MDX once. For MDX-heavy sites using this pattern, e.g. https://github.com/newrelic/docs-website
This translates to the following difference in query running time:
Before this PR:
After this PR:
(image processing also affects those numbers, on a machine with more CPU cores or in Gatsby Cloud where image processing is additionally optimized it can yield even bigger difference)