Skip to content

dex: Avoid unnecessary allocations during history replay - #7136

Merged
nscuro merged 1 commit into
DependencyTrack:mainfrom
nscuro:avoid-unnecessary-allocations
Aug 27, 2026
Merged

nscuro merged 1 commit into
DependencyTrack:mainfrom
nscuro:avoid-unnecessary-allocations

Conversation

@nscuro

@nscuro nscuro commented Aug 27, 2026

Copy link
Copy Markdown
Member

Description

dex: Avoid unnecessary allocations during history replay.

Stops converting the timestamp of every event from Proto Timestamp to Java Instant during replay. Only convert lazily when the timestamp is requested in workflow code.

Stops allocating new RetryPolicy objects for RetryPolicy#ofDefault. Gets called for every activity invocation, including during history replay. Use a constant instead.

Note these are not big memory hogs, they're just unnecessary and avoidable waste.

Addressed Issue

N/A

Additional Details

N/A

Checklist

  • I have read and understand the contributing guidelines
  • This PR fixes a defect, and I have provided tests to verify that the fix is effective
  • This PR implements an enhancement, and I have provided tests to verify that it works as intended
  • This PR introduces changes to the database model, and I have updated the migration changelog accordingly
  • This PR introduces new or alters existing behavior, and I have updated the documentation accordingly
  • This PR is a substantial change (per the ADR criteria), and I have added an ADR under docs/adr/

Stops converting the timestamp of every event from Proto `Timestamp` to Java `Instant` during replay. Only convert lazily when the timestamp is requested in workflow code.

Stops allocating new `RetryPolicy` objects for `RetryPolicy#ofDefault`. Gets called for every activity invocation, including during history replay. Use a constant instead.

Note these are not big memory hogs, they're just unnecessary and avoidable waste.

Signed-off-by: nscuro <nscuro@protonmail.com>
@nscuro nscuro added this to the 5.1 milestone Aug 27, 2026
@nscuro nscuro added the enhancement New feature or request label Aug 27, 2026
@owasp-dt-bot

Copy link
Copy Markdown

✅ Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
✅ Open Source Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@codacy-production

codacy-production Bot commented Aug 27, 2026 •

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics -4 complexity

Metric Results
Complexity -4

View in Codacy

🟢 Coverage 100.00% diff coverage · 0.00% coverage variation

Metric Results
Coverage variation ✅ 0.00% coverage variation (-1.00%)
Diff coverage ✅ 100.00% diff coverage (70.00%)

View coverage diff in Codacy

Coverage variation details
Coverable lines Covered lines Coverage
Common ancestor commit (501627d) 44317 38684 87.29%
Head commit (bb3cd5c) 44319 (+2) 38684 (+0) 87.29% (0.00%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details
Coverable lines Covered lines Diff coverage
Pull request (#7136) 5 5 100.00%

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.

@nscuro
nscuro merged commit c1a46a1 into DependencyTrack:main Aug 27, 2026
22 checks passed
@nscuro
nscuro deleted the avoid-unnecessary-allocations branch August 27, 2026 09:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants