Skip to content

Fix VRAM usage during evaluation - #13

Merged
Mihajlo Linić (MihajloLinic) merged 2 commits into
JetBrains-Research:mainfrom
Jaimeetxebarria:main
Jul 15, 2026
Merged

Fix VRAM usage during evaluation#13
Mihajlo Linić (MihajloLinic) merged 2 commits into
JetBrains-Research:mainfrom
Jaimeetxebarria:main

Conversation

@Jaimeetxebarria

Copy link
Copy Markdown
Contributor

This fixes the unnecessary VRAM usage generated by passing compute_metrics for reporting the privacy budget, by overriding the log method instead. It also adds a new privacy parameter called epsilon_log_mode that can be set to "train", "eval", "both" (default) or "none", which controls when to report the expended privacy budget. I've updated the documentation and created tests for the feature.

Fixes #12

@MihajloLinic

Copy link
Copy Markdown
Collaborator

Sorry for not seeing the pull request earlier! I will check it out now

@MihajloLinic

Copy link
Copy Markdown
Collaborator
image Great job! We knew there was the memory bug somewhere but didn't have time to go around finding it thank you. I will make sure there are no regressions and merge it

Co-authored-by: Junie <junie@jetbrains.com>
@MihajloLinic
Mihajlo Linić (MihajloLinic) merged commit ceb54a4 into JetBrains-Research:main Jul 15, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Epsilon budget reporting generates unnecessary VRAM usage on evaluation

2 participants