Skip to content
#software testing Dataset Open access

Privacy-Utility Trade-offs in Differentially Private Synthetic Tabular Data: a reproducible benchmark on the UCI Heart Disease (Cleveland) dataset

Sep 2026 · Zenodo (CERN European Organization for Nuclear Research)

Abstract

A reproducible benchmark measuring how the utility of differentially private (DP) synthetic tabular data degrades as the privacy budget tightens, and separating the error introduced by the synthesizer from that introduced by the downstream DP estimator. Contents heart_benchmark_results.csv — tidy results, 2,444 rows x 15 columns. One row per (synthesizer, epsilon, replicate, method, statistic), carrying true_value (ground truth computed on the original data), dp_estimate, and non_dp_estimate (a non-private control computed on the same synthetic data). Comparing synth_abs_error with abs_error separates synthesis loss from inference loss. metadata_dictionary.csv — column-by-column data dictionary, including notes on noise layering, provenance, and design conditioning. reproduce_heart_benchmark.R — annotated end-to-end reproduction script, runtime approximately 40 seconds. data/heart_cleveland_clean.csv — cleaned input, 297 complete records. figures/heart_utility_tradeoff.png — four-panel privacy-utility trade-off figure. synthesis_failures.csv — replicate-level synthesis failures with originating error messages. MANUSCRIPT.md and the compiled Data Descriptor manuscript (DOCX). Method. Four DP synthesizers (Gaussian copula, histogram marginals, PATE, Gaussian mixture) across five privacy budgets (epsilon = 0.1, 0.5, 1, 2, 8) and ten Monte Carlo replicates, scored with differentially private descriptive statistics, two hypothesis tests, and linear regression. Master seed 20,260,929, with per-cell seeds derived deterministically so that any single cell reproduces in isolation. Principal finding. The commonly specified regression cholesterol ~ age + resting_blood_pressure is so ill-conditioned on this data that its differentially private coefficients are pure noise at every privacy budget examined: the smallest eigenvalue of the design matrix is 4.09, against 22,019.2 for a publicly centred, intercept-free alternative. This is an 18,691-fold difference in DP sensitivity arising purely from parameterisation, with no change to the data, the response bounds, or the privacy budget. Both specifications are released so that the contrast is auditable. The centred specification yields the expected monotone trade-off, with coefficient MSE falling from 1,695 at epsilon = 0.1 to 1.41 at epsilon = 8. Negative results. The PATE synthesizer shows no privacy-utility trade-off at all: MSE is constant at 23.76 with an interquartile range of 0.02 across an 80-fold change in epsilon. The Gaussian mixture synthesizer releases only 6 of 15 columns, cannot support the categorical tasks, and produces a non-monotone error curve. The copula and histogram-marginal synthesizers fail outright at epsilon = 0.1 in 4 of 50 replicate cells, where the DP-perturbed correlation matrix ceases to be positive definite and the multivariate normal sampler rejects it. Provenance of the source data. Derived from the Cleveland subset of the UCI Heart Disease dataset (UCI Machine Learning Repository, dataset id 45, https://archive.ics.uci.edu/dataset/45/heart+disease). The raw repository release is not redistributed here; only the cleaned and derived files listed above are included. Six records with missing values in the attributes ca (4 records) and thal (2 records) were removed rather than imputed, retaining 297 complete records. Declaration of interests. The creator of this deposit is also the author and maintainer of both DPSynth and DPrivStats, the differentially private software packages evaluated in this benchmark. This is a self-evaluation, declared in full in the associated manuscript (Competing Interests). The benchmark reports unfavourable results for the creator's own packages, including the synthesis failures and structural limitations summarised above. All four synthesizers were run under an identical protocol, using the packages exactly as published on CRAN without modification, and the complete results table is released so that every comparison can be independently re-derived.

View source

Similar papers

#computer vision Review Sep 2017

Agile Software Development Methods: Review and Analysis

This publication proposes a definition and a classification of agile software development approaches and analyses ten software development methods that can be characterized as being "agile" against the defined criterion.

P. Abrahamsson, O. Salo, Jussi Ronkainen et al. · 727 citations · ⚡54
#computer vision Jun 2008

The impact of agile practices on communication in software development

The study shows that agile practices improve both informal and formal communication, but indicates that, in larger development situations involving multiple external stakeholders, a mismatch of adequate communication mechanisms can sometimes even hinder the communication.

M. Pikkarainen, Jukka Haikara, O. Salo et al. · 401 citations · ⚡48
#machine learning Review Open access Oct 2014

Software development in startup companies: A systematic mapping study

The results indicate that software engineering work practices are chosen opportunistically, adapted and configured to provide value under the constrains imposed by the startup context.

Nicolò Paternoster, Carmine Giardino, M. Unterkalmsteiner et al. · 394 citations · ⚡54
#computer vision Review Mar 2008

Agile methods in European embedded software development organisations: a survey on the actual use and usefulness of Extreme Programming and Scrum

The results show that the embedded industry has been able to apply agile methods in its development processes and that the appreciation of the agile methods and their individual practices appears to increase once adopted and applied in practice.

O. Salo, P. Abrahamsson · 238 citations · ⚡9
#computer vision Open access Jul 2017

What happens when software developers are (un)happy

Consequences of happiness and unhappiness that are beneficial and detrimental for developers' mental well-being, the software development process, and the produced artifacts are found.

D. Graziotin, Fabian Fagerholm, Xiaofeng Wang et al. · 236 citations · ⚡13
#computer vision Open access Oct 2004

Mobile-D: an agile approach for mobile application development

The Mobile-D approach is briefly outlined here and the experiences gained from four case studies are discussed, which helped develop an agile development approach for mobile application development.

P. Abrahamsson, Antti Hanhineva, H. Hulkko et al. · 225 citations · ⚡18

Related blog posts

MIT News · Artificial Intelligence Oct 2, 2026

Documenting the tech worker movement

Writing as a participant and researcher, PhD student JS Tan SM ’22 has co-authored a new book about the rise of tech worker protests and the employer backlash that followed.

GPT-Lab Sep 23, 2026

Requirements Don’t Live in Isolation: What We’re Exploring with Req-Space

Requirements in large systems rarely exist in isolation. Their meaning depends on the wider project context - other requirements, policies, decisions, tests, and implementation details. That becomes especially important when AI is used for review, because spotting a possible conflict or gap is only the beginning. ReqSpace explores how AI, visualisation, and connected project context can help reviewers understand those findings, trace the relationships behind them, and focus on the questions that…

GPT-Lab Sep 17, 2026

Beyond Prompt Engineering: The Role of Tacit Knowledge in Software Engineering

AI is making software generation faster, but speed does not remove the need for expertise. As more work is delegated to AI, tacit knowledge may become one of the most important human advantages in software engineering. The post Beyond Prompt Engineering: The Role of Tacit Knowledge in Software Engineering appeared first on GPT-Lab.

We use cookies to run the site and, with your consent, for analytics and to show ads. See our Cookie Policy.