Evaluates how different deep learning model architectures and hyperparameters affect hardware performance across TPU, GPU, and CPU platforms. It probes the interaction between model attributes (size, type, batch size) and hardware bottlenecks like memory bandwidth, compute utilization, and data infeed overhead. Use when the user wants to benchmark on ParaDnn, or asks about evaluating this task. Reports performance.
Scanned 9/11/2026
Install to Claude Code
npx -y skills add qhjqhj00/research-skills-pool --skill paradnn-hardware-bench --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Paradnn Hardware Bench?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/qhjqhj00-paradnn-hardware-bench)More formats (shields.io, HTML) on the badges page.
---
name: paradnn-hardware-bench
description: Evaluates how different deep learning model architectures and hyperparameters affect hardware performance across TPU, GPU, and CPU platforms. It probes the interaction between model attributes (size, type, batch size) and hardware bottlenecks like memory bandwidth, compute utilization, and data infeed overhead. Use when the user wants to benchmark on ParaDnn, or asks about evaluating this task. Reports performance.
metadata:
skill_kind: dataset_eval
source_arxiv: 1907.10701
bibtex_key: wang2019paradnn
confidence: high
---
# paradnn-hardware-bench
> Benchmarking TPU, GPU, and CPU Platforms for Deep Learning — Wang et al. (2019) (arXiv:1907.10701, 2019)
## What this evaluates
Evaluates how different deep learning model architectures and hyperparameters affect hardware performance across TPU, GPU, and CPU platforms. It probes the interaction between model attributes (size, type, batch size) and hardware bottlenecks like memory bandwidth, compute utilization, and data infeed overhead.
## Datasets
- **ParaDnn** — total ?; splits: sweep (-1)
## Metrics
- `performance` **(primary)** — range: other
- Measured as hardware throughput (e.g., operations/sec or images/sec) and FLOPS utilization across varying model configurations. Evaluated at the largest batch size supported by each hardware platform.
## Input / output format
**Input**: Parameterized end-to-end DNN models (FC, CNN, RNN) with variable hyperparameters including number of layers, nodes/filters, input/output dimensions, sequence lengths, vocabulary sizes, and training batch sizes.
**Output**: Performance metrics (throughput, FLOPS utilization, memory bandwidth usage) per hardware platform (TPU, GPU, CPU) for each model configuration.
## Scoring recipe
```python
for config in ParaDnn_sweep:
batch = max_batch_size(hardware, config)
run_model(config, batch, hardware)
record_throughput(hardware, config)
record_flops_utilization(hardware, config)
compare_platforms(throughput, flops_utilization)
```
## Common pitfalls
- Assuming fixed model sizes; ParaDnn explicitly sweeps hyperparameters across wide ranges.
- Ignoring data infeed overhead and memory bandwidth constraints, which heavily limit TPU performance on certain workloads.
- Using batch sizes beyond hardware limits, which causes out-of-memory errors or degraded performance.
## Evidence (verbatim from paper)
> Their limitation is that they only contain today’s deep learning models, which may become obsolete as DL models evolve rapidly. Further, they fail to reveal deep insights into interactions between DL model attributes and hardware performance, since the benchmarks are sparse points in the vast space of deep learning models.
## Citation
```bibtex
@misc{wang2019paradnn,
title={Benchmarking TPU, GPU, and CPU Platforms for Deep Learning},
author={Wang et al. (2019)},
year={2019},
note={arXiv:1907.10701}
}
```
- arXiv: 1907.10701
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!