-
-
Notifications
You must be signed in to change notification settings - Fork 224
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FEATURE: extract content subgraph inmemory caching #5244
FEATURE: extract content subgraph inmemory caching #5244
Conversation
This is not needed anymore because we are now able to flush caches properly because we are not asynchronous anymore
…lly, Does not store subgraphs anymore in memory, but return them on demand
4fdbf0b
to
66193dd
Compare
66193dd
to
99f7cc9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I love it, so many removals and simplifications!
+1 by reading
$uncachedSubgraph = $contentRepository->getContentGraph($nodeAddress->workspaceName)->getSubgraph( | ||
$nodeAddress->dimensionSpacePoint, | ||
VisibilityConstraints::frontend() | ||
); | ||
$subgraph = new ContentSubgraphWithRuntimeCaches($uncachedSubgraph, $this->subgraphCachePool); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we probably need an api way of doing this as thats sometimes the case on the boundary where we dont have a $node yet and cannot use the cr registry
Resolves: #5243