← Latest papers
🤖 machine learning

Position: Zeroth-Order Optimization in Deep Learning Is Underexplored, Not Underpowered

This paper argues that zeroth-order optimization in deep learning is not inherently unscalable but rather underexplored due to myopic design practices, advocating for a paradigm shift toward subspace methods, system-aware advantages, and de-obfuscated evaluations to unlock its potential for large-scale, resource-efficient learning.

Original authors: Sijia Liu, Yicheng Lang, Soumyadeep Pal, Changsheng Wang, Yancheng Huang, Chongyu Fan, James Diffenderfer, Bhavya Kailkhura, Yihua Zhang

Published 2026-05-18
📖 6 min read🧠 Deep dive

Original authors: Sijia Liu, Yicheng Lang, Soumyadeep Pal, Changsheng Wang, Yancheng Huang, Chongyu Fan, James Diffenderfer, Bhavya Kailkhura, Yihua Zhang

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

The Big Idea: It's Not Broken, We Just Haven't Learned How to Use It Yet

Imagine you are trying to find the lowest point in a giant, pitch-black valley (this represents training a complex AI model).

  • The Old Way (First-Order Optimization): You have a magical flashlight that not only shows you the ground but also tells you exactly which way is "down" (the gradient). This is how most AI is trained today. It's fast, but the flashlight requires a massive battery (huge computer memory) and breaks easily if you try to use it on weird, non-standard terrain (like simulators or black-box systems).
  • The "Zeroth-Order" (ZO) Way: You don't have a flashlight. You only have a stick. To figure out which way is down, you poke the ground in different directions with the stick. If the ground feels lower, you step that way. This is Zeroth-Order (ZO) optimization. It uses very little memory and works on any terrain, even if you can't see the ground.

The Problem: For a long time, people thought the "stick method" was too slow and clumsy for big mountains. They believed it would take forever to poke the ground enough times to find the bottom.

The Paper's Claim: The authors say, "Stop! You're judging the stick method unfairly." They argue that ZO isn't weak; it's just underexplored. We've been using the stick in the wrong way (poking every single inch of the ground one by one). If we change how we poke, we can make it just as powerful as the flashlight, but without the heavy battery.


The Six Key Points (The "How-To" Guide)

The authors propose six new ways to think about using the "stick" to make it work better.

1. Don't Poke Randomly Everywhere (P1 & P2)

The Analogy: Imagine you are trying to find the best spot to plant a tree in a massive field.

  • The Mistake: Most people poke the ground randomly in every direction at once. This creates a lot of "noise" (confusion) and requires poking millions of times.
  • The Fix: The paper says, "Be smarter about where you poke." Instead of poking everywhere, poke in specific, structured patterns. Also, realize that poking more times reduces confusion but costs more time. You need to find the perfect balance between "how many pokes" and "how clear the signal is."

2. Use a Compass, Not Just a Stick (P3)

The Analogy: When you poke the ground, you are actually measuring the slope in one specific direction (like a compass needle).

  • The Insight: The authors say we should stop pretending we are just guessing. We should treat these "pokes" as measuring the slope in a specific direction. If we compare our "stick method" against a theoretical "perfect compass" (called a directional derivative), we can see exactly how good our method really is. This helps us stop blaming the tool when the task is actually just really hard.

3. Zoom In on the Important Stuff (P4)

The Analogy: Imagine trying to navigate a city by looking at a map of the entire planet. It's overwhelming.

  • The Fix: Instead of poking the whole planet, zoom in on a small neighborhood (a subspace). The authors suggest that AI models often have hidden patterns where only a few directions matter. If we only poke in those specific "neighborhoods" (low-dimensional subspaces), we get a clear answer with far fewer pokes. It's like navigating a city by only looking at the main streets instead of every single alley.

4. The "Invisible Team" Advantage (P5)

The Analogy: Imagine a team of workers trying to move a heavy couch.

  • The Old Way (Flashlight): They all need to see the exact same blueprint and talk constantly to coordinate. This takes a lot of time and bandwidth.
  • The ZO Way: Because the "stick method" only requires sending a single number (like "it's lower here!") rather than a whole blueprint, the workers can communicate much faster. They can even use a shared secret code (a random seed) to know where to poke without talking. This makes ZO optimization incredibly fast for teams working on different computers, and it saves a lot of energy.

5. Don't Blame the Tool for a Too-Easy Task (P6)

The Analogy: Imagine a student taking a test.

  • The Issue: Sometimes, the teacher gives the student a cheat sheet (called task alignment) that makes the test super easy. The student gets an A, but you don't know if they are smart or just lucky.
  • The Fix: The authors say, "Stop giving the cheat sheet!" We need to test the "stick method" on hard problems where the cheat sheet isn't allowed. If the method still works, then we know the tool is actually powerful. If it fails, we know the tool needs work. This stops us from thinking the tool is great just because the test was rigged.

The Call to Action: What Should We Do Next?

The authors aren't just complaining; they are giving a roadmap for the future:

  1. Change the Rules of the Game: Stop testing these methods with "cheat sheets" (task alignment) and without measuring how many "pokes" (queries) it takes. We need fair tests.
  2. Stop Poking the Whole World: Move away from poking every single parameter. Start poking in smaller, smarter groups (subspaces) or use "spectral" tricks to find the most important directions.
  3. Build New Tools for the Stick: We are currently trying to fit the "stick method" into tools built for the "flashlight." We need to build new computer systems designed specifically for the stick method. These systems would be lighter, faster, and work on cheaper computers.
  4. Look Beyond AI: This method isn't just for AI. It's perfect for things where you can't use a flashlight at all, like:
    • Quantum Computers: Where the laws of physics make "flashlights" (gradients) impossible to use.
    • Scientific Simulators: Where you are testing a physical model (like a bridge or a weather system) and can't mathematically calculate the slope.

The Bottom Line

The paper argues that Zeroth-Order optimization is a Ferrari that we've been driving in a parking lot. We've been using it clumsily, thinking it's slow and weak. But if we build the right roads (systems), drive in the right lanes (subspaces), and stop using cheat sheets (task alignment), it turns out to be a incredibly powerful, memory-efficient, and scalable way to train the next generation of AI.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →