Skip to content

docs: production performance guide#4509

Open
sarahxsanders wants to merge 2 commits intographql:16.x.xfrom
sarahxsanders:performance-optimization
Open

docs: production performance guide#4509
sarahxsanders wants to merge 2 commits intographql:16.x.xfrom
sarahxsanders:performance-optimization

Conversation

@sarahxsanders
Copy link
Contributor

Adds a production performance guide for the performance series, focused on improving GraphQL server performance in production environments. Covers:

  • Identifying bottlenecks
  • Batch database operations
  • Caching strategies
  • Query complexity limiting
  • Database optimization
  • Load testing
  • Additional considerations

@sarahxsanders sarahxsanders requested a review from a team as a code owner November 4, 2025 01:20
duplicate work when the same data appears multiple times in a response.
Replace the simple example with caching for operations specific to your schema.

### Add application-level caching
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would a note somewhere about making sure that an application level cache respects any auth limitations based on any request-specific context. (To be honest, I am aware of the issue, not as well versed in how to mange it.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants