Skip to content

Undo switch to ScheduledDataLoaderRegistry and revert to DgsDataLoaderRegistry - #1709

Merged
srinivasankavitha merged 1 commit into
masterfrom
kavitha/revert-scheduled-dataloader-registry
Nov 13, 2023
Merged

srinivasankavitha merged 1 commit into
masterfrom
kavitha/revert-scheduled-dataloader-registry

Conversation

@srinivasankavitha

Copy link
Copy Markdown
Contributor

Pull Request type

  • Bugfix
  • Feature
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • Other (please describe):

Changes in this PR

This PR reverts a recent change to use ScheduledDataLoaderRegistry introduced in v8.0.0 . We use the delegating wrapper DgsDataLoaderRegistry as was the case prior to v8.0.0 due to this issue.
The ScheduledDataLoaderRegistry creates a new ScheduledExecutorService (even if we use an injected executor) in the builder. This is done per request and ends up using way too much memory for high RPS services.
This change is temporary and will be reverted back to usethe SCheduledDataLoaderRegistry once we have the new release in graphql-java with a fix.

@srinivasankavitha
srinivasankavitha force-pushed the kavitha/revert-scheduled-dataloader-registry branch from a0fe156 to d9e3c9b Compare November 13, 2023 18:22
@srinivasankavitha
srinivasankavitha merged commit ed0af2b into master Nov 13, 2023
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.

1 participant