fix: cache SandboxMetadataDB instance instead of recreating per job#8457
Merged
aldbr merged 1 commit intoDIRACGrid:integrationfrom Feb 16, 2026
Merged
Conversation
chrisburr
force-pushed
the
fix/cache-sandbox-metadata-db
branch
from
8e78e1c to
488e5c7
Compare
aldbr
approved these changes
Feb 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
SandboxMetadataDBinJobSanity.initializeOptimizer()andJobCleaningAgent.initialize()instead of creating a new instance on every callSHOW TABLESquery, and table schema check unnecessarilyBEGINRELEASENOTES
*WorkloadManagement
FIX: cache SandboxMetadataDB instance in JobSanity and JobCleaningAgent to avoid unnecessary DB overhead per job
ENDRELEASENOTES