SISA Training (Sharded, Isolated, Sliced, and Aggregated) is a machine learning framework that preemptively partitions a training dataset into multiple non-overlapping data shards. Each shard is used to train an independent constituent model in isolation, and these models are aggregated to form a final prediction. When a data deletion request is received, only the specific shard containing the target data point requires retraining, dramatically reducing the computational cost compared to full model retraining.
Glossary
SISA Training

What is SISA Training?
SISA Training is a machine unlearning framework that partitions data into disjoint shards to limit the scope of retraining required when a deletion request targets a single data point.
The framework introduces a trade-off between unlearning speed and model accuracy. By slicing each shard further into incremental training slices and archiving checkpoints, SISA enables rapid epoch rewinding to a state before the target data was introduced. This architecture transforms the right to be forgotten from a prohibitively expensive operation into a bounded, incremental maintenance task, providing a practical path to compliance for large-scale production systems.
Key Characteristics of SISA Training
SISA (Sharded, Isolated, Sliced, and Aggregated) training is a machine unlearning framework that partitions data into disjoint shards to limit the scope of retraining required when a deletion request targets a single data point.
Data Sharding
The training dataset is horizontally partitioned into mutually exclusive, non-overlapping shards. Each shard is assigned to an independent constituent model, ensuring that any single data point influences only one model replica. This isolation is the foundational mechanism that constrains the blast radius of a deletion request.
- Shards are typically created using random uniform partitioning
- Each shard trains a separate model instance from scratch
- No data point appears in more than one shard
- The number of shards directly trades off unlearning speed against model accuracy
Isolated Submodels
Each shard trains a completely independent model replica with no weight sharing, gradient exchange, or distributed synchronization during training. This architectural isolation guarantees that when a deletion request arrives, only the single submodel that ingested the target data requires modification.
- Models are trained asynchronously on separate hardware
- No inter-model communication occurs during training
- Isolation eliminates cross-contamination between shards
- Enables parallel, non-blocking unlearning operations
Incremental Slicing
Within each shard, training data is further divided into temporal slices and checkpoints are saved at slice boundaries. When unlearning is required, the affected submodel is rolled back to the checkpoint immediately preceding the slice containing the target data, then retrained only on the remaining slices.
- Slices act as intra-shard recovery points
- Reduces retraining cost from full shard to a subset of slices
- Checkpoint frequency determines the granularity of rollback
- Balances storage overhead against unlearning latency
Aggregated Inference
At inference time, predictions from all constituent submodels are combined through an aggregation function to produce a single output. The ensemble nature of SISA provides built-in redundancy, as the removal of one submodel for retraining only marginally degrades overall performance during the unlearning window.
- Common aggregation: majority voting for classification
- For regression: arithmetic mean of submodel outputs
- Ensemble provides fault tolerance during unlearning
- Inference latency scales linearly with the number of shards
Exact Unlearning Guarantee
SISA provides exact unlearning—the retrained model is mathematically identical to one trained from scratch without the deleted data. Because each shard is independent, retraining a single shard on its remaining data produces a distribution that matches the gold standard of full retraining for that partition.
- No approximation error or statistical leakage
- Verifiable through membership inference attack auditing
- Satisfies strict regulatory requirements under GDPR Article 17
- Contrasts with approximate methods like gradient ascent
Computational Tradeoffs
The primary cost of SISA is increased training overhead proportional to the number of shards, as each submodel must be trained independently. However, this upfront investment is amortized across the model lifecycle by dramatically reducing the cost of each subsequent unlearning operation.
- Training cost: S × cost of single model
- Unlearning cost: 1/S × cost of full retraining
- Storage overhead: S model checkpoints plus slice archives
- Optimal S balances training budget against expected deletion frequency
Frequently Asked Questions
Clear, technically precise answers to the most common questions about Sharded, Isolated, Sliced, and Aggregated training for efficient machine unlearning.
SISA training (Sharded, Isolated, Sliced, and Aggregated) is a machine learning framework that partitions a dataset into disjoint, non-overlapping shards to limit the scope of retraining required for data deletion. Each shard trains an independent constituent model in complete isolation. Within a shard, data is further divided into slices and training occurs incrementally, with model checkpoints saved after each slice. The final prediction is produced by an aggregation mechanism—typically majority voting or averaging—that combines the outputs of all constituent models. When a deletion request targets a single data point, only the specific model trained on the shard containing that point must be retrained from the last clean checkpoint before the affected slice, dramatically reducing computational cost compared to full retraining from scratch.
SISA Training vs. Other Unlearning Approaches
A comparative analysis of SISA Training against exact unlearning, approximate unlearning, and retraining from scratch across key operational dimensions.
| Feature | SISA Training | Exact Unlearning | Retraining from Scratch |
|---|---|---|---|
Unlearning Guarantee | Exact per shard | Provably exact | Gold standard exact |
Computational Cost | O(1) per request | O(n) per request | O(n) full retraining |
Retraining Scope | Single shard only | Full model | Full model |
Supports Incremental Deletion | |||
Requires Data Sharding | |||
Verification Complexity | Shard-level audit | Statistical bound | Trivial verification |
Storage Overhead | k × model size | 1 × model size | 1 × model size |
Deletion Latency | < 1 min per shard | Hours to days | Hours to weeks |
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Related Terms
Explore the core mechanisms and related concepts that constitute the Sharded, Isolated, Sliced, and Aggregated training framework for efficient machine unlearning.
Data Sharding
The foundational step of SISA training. The original dataset is horizontally partitioned into mutually exclusive, disjoint shards. Each shard is used to train an independent constituent model. This isolation ensures that a deletion request for a single data point affects only one shard, limiting the scope of retraining. The number of shards creates a direct trade-off between unlearning granularity and the overhead of managing multiple models.
Data Slicing
Within each shard, data is further divided into temporal slices to create incremental checkpoints. The model for a shard is trained slice-by-slice, and its architecture and parameters are saved after each slice. When a deletion request arrives, the system can roll back to the checkpoint immediately before the target data was introduced, minimizing the computational cost of retraining to only the affected slices.
Incremental Aggregation
The final prediction is formed by aggregating the outputs of the independent constituent models. Common strategies include:
- Majority voting for classification tasks
- Averaging output probabilities or logits
- A trainable meta-model that learns to weight shard outputs This modular ensemble architecture ensures that the removal or retraining of one shard's model does not require touching the others.
Exact Unlearning Guarantee
SISA provides an exact unlearning guarantee. Because the data point to be deleted is contained within exactly one shard, retraining only that shard from the clean checkpoint produces a final aggregated model that is mathematically identical to one trained from scratch on the remaining dataset. This satisfies the strictest regulatory requirements for data removal without the prohibitive cost of full retraining.
Computational Trade-offs
The efficiency of SISA is governed by the sharding and slicing configuration:
- More shards: Faster unlearning (smaller retraining scope) but higher inference latency and storage costs.
- More slices: Finer granularity for rollback but increased checkpoint storage overhead. The optimal configuration balances deletion latency against operational costs for the specific deployment context.
SISA vs. Federated Unlearning
While SISA partitions data into explicit, centrally managed shards, federated unlearning deals with removing a client's entire contribution from a global model trained across decentralized devices. SISA's approach is a centralized, deterministic strategy, whereas federated unlearning often relies on approximate methods or historical gradient storage. Both address the same core problem of data isolation for deletion but in fundamentally different architectural contexts.

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us