8000 chore(dal): Test if we unintentionally regress node/edge size by jkeiser · Pull Request #6155 · systeminit/si · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

chore(dal): Test if we unintentionally regress node/edge size #6155

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

8000
Merged
merged 1 commit into from
May 19, 2025

Conversation

jkeiser
Copy link
Contributor
@jkeiser jkeiser commented May 19, 2025

This adds a unit test which will fail if NodeWeight or EdgeWeight gets bigger. It also checks individual NodeWeight sizes so we can get a sense of what's impacting node size.

If you increase the size of one of the individual NodeWeight variants, it can have multiplicative effects beyond just the type you modified: increasing the biggest variants will increase the size of NodeWeight itself, which effectively increases all node sizes (since petgraph reserves space for a NodeWeight, not an individual variant). Increasing smaller node weights will have minimal impact on runtime space requirements.

Testing

  • Check if this works in debug builds as well as release builds

Copy link
github-actions bot commented May 19, 2025

Dependency Review

✅ No vulnerabilities or OpenSSF Scorecard issues found.

Scanned Files

None

@github-actions github-actions bot added the A-dal label May 19, 2025
@jkeiser jkeiser force-pushed the jkeiser/node-size branch from af929f5 to 8495d43 Compare May 19, 2025 17:57
@jkeiser jkeiser requested review from zacharyhamm and nickgerace May 19, 2025 19:19
@jkeiser jkeiser added this pull request to the merge queue May 19, 2025
Merged via the queue into main with commit c9e4a1a May 19, 2025
10 checks passed
@jkeiser jkeiser deleted the jkeiser/node-size branch May 19, 2025 22:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0