AJ-1498: tracing and isolation level for updateStatisticsCache #2652
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.
Ticket: https://broadworkbench.atlassian.net/browse/AJ-1498
More optimizations and debuggability for the entity statistics cache.
updateStatisticsCache
to be ReadCommitted. This is probably moot, since this method is only called fromsweep()
, and we set the outer transaction insweep()
to ReadCommitted in AJ-1498: reduce transaction isolation level for entity metadata #2650. But, it helps for code readability and future-proofing.sweep()
. This is likely to confirm previous knowledge thatgetAttrNamesAndEntityTypes
is slow, but it'll be good to see empirical data.Reviewer: I suggest ignoring whitespace in the diff; auto-formatter changed a bunch
PR checklist
model/
, then you should publish a new officialrawls-model
and updaterawls-model
in Orchestration's dependencies.