Skip to content

Commit 992fafe

Browse files
authored
Add DPack missing badges (#316)
1 parent fd07ac7 commit 992fafe

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

source/_data/SymbioticLab.bib

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1902,6 +1902,8 @@ @InProceedings{dpack:eurosys25
19021902
year = {2025},
19031903
publist_confkey = {EuroSys'25},
19041904
publist_topic = {Systems + AI},
1905+
publist_badge = {Artifacts Available},
1906+
publist_badge = {Artifacts Functional},
19051907
publist_link = {paper || dpack-eurosys25.pdf},
19061908
publist_abstract = {
19071909
Machine learning (ML) models can leak information about users, and differential privacy (DP) provides a rigorous way to bound that leakage under a given budget. This DP budget can be regarded as a new type of compute resource in workloads of multiple ML models training on user data. Once it is used, the DP budget is forever consumed. Therefore, it is crucial to allocate it most efficiently to train as many models as possible. This paper presents a scheduler for privacy that optimizes for efficiency. We formulate privacy scheduling as a new type of multidimensional knapsack problem, called privacy knapsack, which maximizes DP budget efficiency. We show that privacy knapsack is NP-hard, hence practical algorithms are necessarily approximate. We develop an approximation algorithm for privacy knapsack, DPack, and evaluate it on microbenchmarks and on a new, synthetic private-ML workload we developed from the Alibaba ML cluster trace. We show that DPack: (1) often approaches the efficiency-optimal schedule, (2) consistently schedules more tasks compared to a state-of-the-art privacy scheduling algorithm that focused on fairness (1.3–1.7X in Alibaba, 1.0–2.6X in microbenchmarks), but (3) sacrifices some level of fairness for efficiency. Therefore, using DPack, DP ML operators should be able to train more models on the same amount of user data while offering the same privacy guarantee to their users. }

0 commit comments

Comments
 (0)