Papers › AutoPEFT: Automatic Configuration Search for Parameter-Efficient Fine-Tuning

AutoPEFT: Automatic Configuration Search for Parameter-Efficient Fine-Tuning

28 Jan 2023arXiv:2301.12132archive 2025-07-28

Han Zhou, Xingchen Wan, Ivan Vulić, Anna Korhonen

Large pretrained language models are widely used in downstream NLP tasks via task-specific fine-tuning, but such procedures can be costly. Recently, Parameter-Efficient Fine-Tuning (PEFT) methods have achieved strong task performance while updating much fewer parameters than full model fine-tuning (FFT). However, it is non-trivial to make informed design choices on the PEFT configurations, such as their architecture, the number of tunable parameters, and even the layers in which the PEFT modules are inserted. Consequently, it is highly likely that the current, manually designed configurations are suboptimal in terms of their performance-efficiency trade-off. Inspired by advances in neural architecture search, we propose AutoPEFT for automatic PEFT configuration selection: we first design an expressive configuration search space with multiple representative PEFT modules as building blocks. Using multi-objective Bayesian optimisation in a low-cost setup, we then discover a Pareto-optimal set of configurations with strong performance-cost trade-offs across different numbers of parameters that are also highly transferable across different tasks. Empirically, on GLUE and SuperGLUE tasks, we show that AutoPEFT-discovered configurations significantly outperform existing PEFT methods and are on par or better than FFT without incurring substantial training efficiency costs.

PaperPDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 13 code samples: 12 from 1 repository linked to this paper, 1 identical to code harvested from another paper's repository. Across all 13: 11 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 3 honoured, 0 violated, 4 with no contract checked; 4 where Syntology's instrument failed) · 2 unverified. Where Syntology's instrument failed: 3 where our contract draft was wrong; 1 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: official repository: 12 samples from 1 repository, 10 ran (7 with no instrument failure; 3 where Syntology's instrument failed); 1 identical to code first harvested elsewhere. The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written between 2026-09-24 and 2026-09-26 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed. 1 of the 11 samples that ran has no recorded date.

cambridgeltl/autopeft officialmentioned in papermentioned on GitHubjaxApache-2.0Syntology: 12 samples, 10 ran (3 instrument-failed) · 2 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

13 samples harvested: 11 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 3 honoured, 0 violated, 4 with no contract checked; 4 where Syntology's instrument failed) · 2 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

3ran · honoured contract
3ran · our draft was wrong
1ran; the contract check could not run
4ran
2unverified

Licence: 13 of the 13 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from cambridgeltl/autopeft. 1 sample is listed last, in a group without a repository. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

cambridgeltl/autopeft official repository 12 samples, 10 ran (3 instrument-failed) · 2 unverified
acc_and_f1 in 39 papers glue_metrics.py ran; the contract check could not run (RAISES) Apache-2.0 recorded; this copy not marked cleared · pointer only · 454817035cd7e70d · report fixture: signature preds:ndarray/1/int, labels:ndarray/1/int · returned dict · level recorded 2026-09-24
gelu_fast in 39 papers adapter-transformers-adapters3.1.0/src/transformers/activations_tf.py ran · honoured contract fingerprinted Apache-2.0 recorded; this copy not marked cleared · pointer only · 37a5eed2dbd663ca · report fixture: signature x:EagerTensor/2/float · returned EagerTensor · level recorded 2026-09-26
get_all_checkpoint adapterhub/nas_search.py ran Apache-2.0 recorded; this copy not marked cleared · pointer only · 2f0f77422d5933be · report fixture: signature folder:str/0/str · returned list · level recorded 2026-09-25
get_kernel in 18 papers adapterhub/bo/models.py ran Apache-2.0 recorded; this copy not marked cleared · pointer only · 8f025929c3e1325b · report fixture: signature use_ard:bool/0/bool, use_ard_binary:bool/0/bool, non_binary_indices:NoneType/0/?, binary_indices:NoneType/0/? · returned ScaleKernel · level recorded 2026-09-25
get_logger in 383 papers logger.py ran · our draft was wrong Apache-2.0 recorded; this copy not marked cleared · pointer only · b6d6bcb982b768cc · report fixture: signature name:str/0/str · returned Logger · level recorded 2026-09-25
mish in 95 papers
census: 5 implementations from 8 papers, 1 distinct output on one shared input
adapter-transformers-adapters3.1.0/src/transformers/activations_tf.py ran · honoured contract Apache-2.0 recorded; this copy not marked cleared · pointer only · cc8c8c3ebf0c343f · report fixture: signature x:ndarray/2/float · returned EagerTensor · level recorded 2026-09-26
pearson_and_spearman in 9 papers glue_metrics.py ran · our draft was wrong fingerprinted Apache-2.0 recorded; this copy not marked cleared · pointer only · e3e13638a674e4b1 · report fixture: signature preds:ndarray/1/float, labels:ndarray/1/float · returned dict · level recorded 2026-09-24
quick_gelu in 43 papers adapter-transformers-adapters3.1.0/src/transformers/activations_tf.py ran · honoured contract fingerprinted Apache-2.0 recorded; this copy not marked cleared · pointer only · e2d56cb91f999bef · report fixture: signature x:EagerTensor/2/float · returned EagerTensor · level recorded 2026-09-26
split_datasets adapterhub/nas_search.py ran Apache-2.0 recorded; this copy not marked cleared · pointer only · f247d1c0140d8564 · report fixture: signature train_ds:MockDataset/0/?, n:NoneType/0/? · returned tuple · level recorded 2026-09-25
split_datasets adapterhub/run_glue.py ran Apache-2.0 recorded; this copy not marked cleared · pointer only · c2b46bdd4073aaa8 · report fixture: signature train_ds:MockDataset/0/?, n:NoneType/0/? · returned tuple · level recorded 2026-09-25
get_EI adapterhub/bo/models.py unverified Apache-2.0 recorded; this copy not marked cleared · pointer only · 280a696268513b28 · report
simple_accuracy in 66 papers glue_metrics.py unverified Apache-2.0 recorded; this copy not marked cleared · pointer only · 83eba990d34db6a2 · report
Repository not located 1 sample, 1 ran (1 instrument-failed) · 0 unverified
1 sample is identical to code Syntology harvested from another paper's repository; this paper's own copy was not located, so no repository is named and no licence is recorded.
kronecker_product in 9 papers
census: 2 implementations from 6 papers, 1 distinct output on one shared input this sample: bucket 1 of 1, arg 1: rank 3, kind float, dtype float32 · arg 2: rank 3, kind float, dtype float32
repository not located ran · our draft was wrong fingerprinted licence of this copy not recorded · 54fa343f001c7cff · report fixture: signature a:Tensor/3/float, b:Tensor/3/float · returned Tensor · level recorded, date not recorded

Tasks

Bayesian OptimisationNeural Architecture Searchparameter-efficient fine-tuning

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections