Papers › Provably Faster Algorithms for Bilevel Optimization

Provably Faster Algorithms for Bilevel Optimization

8 Jun 2021NeurIPS 2021 12arXiv:2106.04692archive 2025-07-28

Junjie Yang, Kaiyi Ji, Yingbin Liang

Bilevel optimization has been widely applied in many important machine learning applications such as hyperparameter optimization and meta-learning. Recently, several momentum-based algorithms have been proposed to solve bilevel optimization problems faster. However, those momentum-based algorithms do not achieve provably better computational complexity than 𝒪(ϵ⁻²) of the SGD-based algorithm. In this paper, we propose two new algorithms for bilevel optimization, where the first algorithm adopts momentum-based recursive iterations, and the second algorithm adopts recursive gradient estimations in nested loops to decrease the variance. We show that both algorithms achieve the complexity of 𝒪(ϵ^(-1.5)), which outperforms all existing algorithms by the order of magnitude. Our experiments validate our theoretical results and demonstrate the superior empirical performance of our algorithms in hyperparameter applications.

PaperPDFConference PDFCodeCode Syntology ranMethod as code

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

By repository: official repository: 9 samples from 1 repository, 7 ran (2 with no instrument failure; 5 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 on 2026-09-22 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed. 7 of the 8 samples that ran have no recorded date.

JunjieYang97/MRVRBO officialmentioned in papermentioned on GitHubpytorchSyntology: 9 samples, 7 ran (5 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

10 samples harvested: 8 ran (of which 0 constructed an object rather than computing a result; 2 with no instrument failure: 2 honoured, 0 violated, 0 with no contract checked; 6 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 has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

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

Licence: 1 of the 10 samples is 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 JunjieYang97/MRVRBO. 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.

JunjieYang97/MRVRBO official repository 9 samples, 7 ran (5 instrument-failed) · 2 unverified
cat_list_to_tensor in 7 papers hypergrad/CG_torch.py ran · honoured contract MIT (permissive) · 3ed1406329714c3f · report fixture: signature list_tx:list/1/Tensor · returned Tensor · level recorded, date not recorded
cg in 10 papers hypergrad/CG_torch.py ran · our draft was wrong MIT (permissive) · 31f282d2a7c181bb · report fixture: signature Ax:callable/0/?, b:list/1/Tensor, max_iter:int/0/int, epsilon:float/0/float · returned list · level recorded, date not recorded
fixed_point in 7 papers hypergrad/hypergradients.py ran · our draft was wrong MIT (permissive) · 11d924c279d6166a · report fixture: signature params:list/1/Tensor, hparams:list/1/Tensor, K:int/0/int, fp_map:callable/0/?, outer_loss:callable/0/?, tol:float/0/float, set_grad:bool/0/bool, stochastic:bool/0/bool · returned list · level recorded, date not recorded
mstsa stocBiO.py ran; the contract check could not run (RAISES) MIT (permissive) · 2d1dc63491a58c81 · report fixture: signature prerious_update:Tensor/1/float, eta:float/0/float, val_data_list:tuple/1/list, args:Args/0/?, params:Tensor/1/float, params_next:Tensor/1/float, hparams:Tensor/1/float, hparams_old:Tensor/1/float, out_f:callable/0/?, reg_f:callable/0/? · returned Tensor · level recorded 2026-09-22
reverse in 15 papers hypergrad/hypergradients.py ran · honoured contract MIT (permissive) · 52b6f88728db5c40 · report fixture: signature params_history:list/1/list, hparams:list/1/Tensor, update_map_history:list/1/callable, outer_loss:callable/0/?, set_grad:bool/0/bool · returned list · level recorded, date not recorded
reverse_unroll in 5 papers hypergrad/hypergradients.py ran · our draft was wrong MIT (permissive) · 677c8518ad1a22c9 · report fixture: signature params:list/1/Tensor, hparams:list/1/Tensor, outer_loss:callable/0/?, set_grad:bool/0/bool · returned tuple · level recorded, date not recorded
stocbio stocBiO.py ran; the contract check could not run (RAISES) · metamorphic tier: invariant MIT (permissive) · e8238fd3ed908a9f · report fixture: signature params:Tensor/2/float, hparams:Tensor/1/float, val_data_list:tuple/1/list, args:Args/0/?, out_f:callable/0/?, reg_f:callable/0/? · returned Tensor · level recorded, date not recorded
mstsa stocBiO.py unverified MIT (permissive) · 26aebb9780915816 · report
stable stocBiO.py unverified MIT (permissive) · 149effd1caaad2cb · 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.
loss_train_avg repository not located ran; the contract check could not run (RAISES) · metamorphic tier: invariant licence of this copy not recorded · d46ee4443d27d233 · report fixture: signature data_loader:list/1/tuple, parameters:Tensor/2/float, device:device/0/?, batch_num:int/0/int · returned Tensor · level recorded, date not recorded

Method as code Syntology

What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it.

1 assembly on this paper: 1 harvested, 0 generated.

harvested Assembly for momentum-based recursive iterations algorithm (graph method: momentum-based recursive iterations algorithm). 4 bricks; individually on a fixture: 4 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 4 where Syntology's instrument failed) · 0 unverified. The assembly has not been run end-to-end.

  1. mstsa entry · level 1 · ran; the contract check could not run (RAISES) · 2d1dc63491a58c81
  2. stocbio update_rule · level 1 · ran; the contract check could not run (RAISES) · e8238fd3ed908a9f
  3. gradient_fy helper · level 1 · ran · our draft was wrong · b233bbdedd873c21
  4. gradient_gy helper · level 1 · ran · our draft was wrong · cda14929afcae4b3

Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="2106.04692") returns these assemblies with each brick's role and wiring (how to connect).

Tasks

Bilevel OptimizationHyperparameter OptimizationMeta-Learning

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