Files changed (2) hide show
  1. README.md +106 -0
  2. ado-sfttrainer-v1-0-0.csv +3 -0
README.md ADDED
@@ -0,0 +1,106 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ ---
2
+ language:
3
+ - "en" # Example: fr
4
+ license: "apache-2.0" # Example: apache-2.0 or any license from https://hf.co/docs/hub/
5
+ tags:
6
+ - "benchmark"
7
+ - "fine-tuning" # Example: audio
8
+ - "performance" # Example: bio
9
+ - "LLM" # Example: natural-language-understanding
10
+ - "configuration" # Example: birds-classification
11
+ annotations_creators:
12
+ - "expert-generated"
13
+ - "ado" # Example: crowdsourced, found, expert-generated, machine-generated
14
+ language_details: "en-US" # Example: en-US
15
+ pretty_name: "LLMFineTuningBench"
16
+ size_categories:
17
+ - ">15K" # Example: n<1K, 100K<n<1M, …
18
+ task_categories: # Full list at https://github.com/huggingface/huggingface.js/blob/main/packages/tasks/src/pipelines.ts
19
+ - "tabular-regression" # Example: question-answering
20
+ - "tabular-classification" # Example: image-classification
21
+ task_ids:
22
+ - "tabular-single-column-regression" # Example: extractive-qa
23
+ - "tabular-multi-class-classification" # Example: multi-class-image-classification
24
+ configs: # Optional. This can be used to pass additional parameters to the dataset loader, such as `data_files`, `data_dir`, and any builder-specific parameters
25
+ - config_name: "default" # Name of the dataset subset, if applicable. Example: default
26
+ data_files:
27
+ - split: "all" # Example: train
28
+ path: "ado-sfttrainer-v1-0-0.csv" # Example: data.csv
29
+ ---
30
+
31
+ # Dataset Card for LLMFineTuningBench
32
+
33
+ A dataset of over 15,000 LLM fine-tuning experiments, capturing detailed performance metrics from jobs run on high-performance computing (HPC) clusters. It spans a wide range of models, fine-tuning methods, and hardware configurations, and is intended to support research on predictive resource allocation, performance optimization, and cost estimation for LLM fine-tuning workloads.
34
+
35
+ ## Dataset Details
36
+
37
+ ### Dataset Description
38
+
39
+ The rapid adoption of Large Language Models (LLMs) has led to a surge in fine-tuning activities to adapt these models for specific tasks. However, selecting the optimal hardware and software configuration for fine-tuning is a complex, multi-dimensional problem that can lead to significant resource wastage and computational overhead. To address this challenge, we introduce a comprehensive dataset of over 15,000 LLM fine-tuning experiments. The dataset captures detailed performance metrics from jobs executed on high-performance computing clusters, covering a wide range of models, fine-tuning methods, and hardware configurations.
40
+
41
+ ### Dataset Sources
42
+
43
+ <!-- Provide the basic links for the dataset. -->
44
+
45
+ The dataset was collected by systematically exploring the parameter space of LLM fine-tuning across different hardware and software configurations on a high-performance cluster equipped with GPUs. This exploration was conducted using IBM's [ado (accelerated discovery orchestrator)](https://ibm.github.io/ado/) framework. ado features multiple [actuators](https://ibm.github.io/ado/actuators/working-with-actuators/) for executing experiments and collecting data.
46
+
47
+ The data for LLM Fine-tuning benchmarking was collected by the [SFTTrainer actuator](https://ibm.github.io/ado/actuators/sft-trainer/). Under the hood, this actuator wraps the [fms-hf-tuning](https://github.com/foundation-model-stack/fms-hf-tuning) library, which itself builds on the [`SFTTrainer` API from Hugging Face Transformers](https://huggingface.co/docs/trl/sft_trainer). The data is collected using AIM (AI Metadata) to capture profiling metadata during training runs.
48
+
49
+ - **Repository:** [ado SFTTrainer](https://github.com/IBM/ado/blob/main/plugins/actuators/sfttrainer/ado_actuators/sfttrainer/README.md)
50
+
51
+ ## Uses
52
+
53
+ This dataset is intended to support the development of predictive models that map a proposed job configuration (model, hardware, method) to expected throughput and resource utilization — enabling "cost-calculator" or recommendation tools that guide users toward efficient fine-tuning setups.
54
+
55
+ ### Direct Use
56
+
57
+ - Transfer learning approaches
58
+ - Performance prediction models
59
+ - Handling categorical configuration space expansion
60
+ - Sample-efficient model building strategies
61
+
62
+ See [ado Autoconf](https://github.com/IBM/ado/tree/main/plugins/custom_experiments/autoconf) for examples of how this data was used for building predictive models for automated configuration of resources for fine-tuning workloads
63
+
64
+ ## Dataset Structure
65
+
66
+ These columns are produced from the data collected by the SFTTrainer actuator. The parameter descriptions have been sourced from the [ado SFTTrainer actuator documentation](https://ibm.github.io/ado/actuators/sft-trainer/#finetune_full_benchmark-v100).
67
+
68
+ In case of any discrepancy, please refer to the actuator documentation for the most accurate and up-to-date information.
69
+ Key columns in the dataset:
70
+
71
+ | Column | Description |
72
+ | --- | --- |
73
+ | `model_name` | Name of the base LLM (e.g., `llama3-8b`, `mixtral-8x7b-instruct-v0.1`) |
74
+ | `method` | Fine-tuning technique used: `full`, `lora`, or `gptq-lora` |
75
+ | `number_gpus` | Number of GPUs allocated for the job |
76
+ | `gpu_model` | GPU model used (e.g., `L40S`) |
77
+ | `batch_size` | Number of samples processed per training step |
78
+ | `tokens_per_sample` | Sequence length of each sample |
79
+ | `is_valid` | Binary flag (1 or 0) indicating whether the run completed successfully |
80
+ | `dataset_tokens_per_second` | Primary throughput metric — tokens processed per second from the dataset; the most reliable performance measure |
81
+
82
+ Other columns capture additional metrics such as GPU memory utilization, GPU compute utilization, GPU power draw, and total training runtime.
83
+
84
+ ## Dataset Creation
85
+
86
+ #### Data Collection and Processing
87
+
88
+ We benchmarked **15,154 jobs**, varying parameters of `SFTTrainer` including the base model, fine-tuning method, number of GPUs, and batch size. Training data consisted of random text, since the primary goal was to measure computational performance rather than model accuracy — the resulting fine-tuned model weights were discarded after each run.
89
+
90
+ ## Citation [optional]
91
+
92
+ If you use this dataset, please cite it as:
93
+ ```
94
+ @misc{lotito26finetuning,
95
+ title={LLM Fine-Tuning Benchmark Dataset},
96
+ author={Lotito, Daniele and Vassiliadis, Vassilis and
97
+ Pomponio, Alessandro and Venugopal, Srikumar and Johnston, Michael},
98
+ howpublished={Hugging Face Datasets},
99
+ url = {https://huggingface.co/datasets/ibm-research/LLMFineTuningBench/},
100
+ year={2026}
101
+ }
102
+ ```
103
+
104
+ ## Contact Information
105
+
106
+ For any comments or questions, please email [Daniele Lotito](mailto:daniele.lotito@ibm.com), [Vassilis Vassiliadis](mailto:vassilis.vassiliadis@ibm.com) and [Srikumar Venugopal](mailto:srikumarv@ie.ibm.com).
ado-sfttrainer-v1-0-0.csv ADDED
@@ -0,0 +1,3 @@
 
 
 
 
1
+ version https://git-lfs.github.com/spec/v1
2
+ oid sha256:b905ec24d42a4aae0558b364d0db3147da691ae2b21cdaef4263d6b61d56328c
3
+ size 16992661