递归在显式管理堆栈的情况下可能更快，就像你提到的排序或二叉树算法一样。

我曾经遇到过这样的情况，用Java重写递归算法会让它变慢。

因此，正确的方法是首先以最自然的方式编写它，只在分析显示它至关重要时进行优化，然后衡量假定的改进。

一般来说，不，在任何具有两种形式的可行实现的实际使用中，递归不会比循环快。我的意思是，当然，你可以编写出花费很长时间的循环，但是有更好的方法来实现相同的循环，可以通过递归来实现相同的问题。

关于原因，你一针见血;创建和销毁堆栈帧比简单的跳转代价更大。

但是，请注意我所说的“在两种形式中都有可行的实现”。对于像许多排序算法这样的事情，往往没有一种非常可行的方法来实现它们，因为它不能有效地建立自己的堆栈版本，因为生成子“任务”是这个过程固有的一部分。因此，递归可能和试图通过循环实现算法一样快。

编辑:这个答案是假设非函数式语言，其中大多数基本数据类型是可变的。它不适用于函数式语言。

递归比循环快吗?

不，迭代总是比递归快。(冯·诺依曼架构)

解释:

如果你从头开始构建一个通用计算机的最小操作，“迭代”首先作为一个构建块，比“递归”更少的资源密集型，因此更快。

从头开始建造一台伪计算机:

问问你自己:你需要什么来计算一个值，即遵循一个算法并得到一个结果?

我们将建立一个概念层次结构，从头开始，首先定义基本的核心概念，然后用这些概念构建第二级概念，以此类推。

First Concept: Memory cells, storage, State. To do something you need places to store final and intermediate result values. Let’s assume we have an infinite array of "integer" cells, called Memory, M[0..Infinite]. Instructions: do something - transform a cell, change its value. alter state. Every interesting instruction performs a transformation. Basic instructions are: a) Set & move memory cells store a value into memory, e.g.: store 5 m[4] copy a value to another position: e.g.: store m[4] m[8] b) Logic and arithmetic and, or, xor, not add, sub, mul, div. e.g. add m[7] m[8] An Executing Agent: a core in a modern CPU. An "agent" is something that can execute instructions. An Agent can also be a person following the algorithm on paper. Order of steps: a sequence of instructions: i.e.: do this first, do this after, etc. An imperative sequence of instructions. Even one line expressions are "an imperative sequence of instructions". If you have an expression with a specific "order of evaluation" then you have steps. It means than even a single composed expression has implicit “steps” and also has an implicit local variable (let’s call it “result”). e.g.: 4 + 3 * 2 - 5 (- (+ (* 3 2) 4 ) 5) (sub (add (mul 3 2) 4 ) 5) The expression above implies 3 steps with an implicit "result" variable. // pseudocode 1. result = (mul 3 2) 2. result = (add 4 result) 3. result = (sub result 5) So even infix expressions, since you have a specific order of evaluation, are an imperative sequence of instructions. The expression implies a sequence of operations to be made in a specific order, and because there are steps, there is also an implicit "result" intermediate variable. Instruction Pointer: If you have a sequence of steps, you have also an implicit "instruction pointer". The instruction pointer marks the next instruction, and advances after the instruction is read but before the instruction is executed. In this pseudo-computing-machine, the Instruction Pointer is part of Memory. (Note: Normally the Instruction Pointer will be a “special register” in a CPU core, but here we will simplify the concepts and assume all data (registers included) are part of “Memory”) Jump - Once you have an ordered number of steps and an Instruction Pointer, you can apply the "store" instruction to alter the value of the Instruction Pointer itself. We will call this specific use of the store instruction with a new name: Jump. We use a new name because is easier to think about it as a new concept. By altering the instruction pointer we're instructing the agent to “go to step x“. Infinite Iteration: By jumping back, now you can make the agent "repeat" a certain number of steps. At this point we have infinite Iteration. 1. mov 1000 m[30] 2. sub m[30] 1 3. jmp-to 2 // infinite loop Conditional - Conditional execution of instructions. With the "conditional" clause, you can conditionally execute one of several instructions based on the current state (which can be set with a previous instruction). Proper Iteration: Now with the conditional clause, we can escape the infinite loop of the jump back instruction. We have now a conditional loop and then proper Iteration 1. mov 1000 m[30] 2. sub m[30] 1 3. (if not-zero) jump 2 // jump only if the previous // sub instruction did not result in 0 // this loop will be repeated 1000 times // here we have proper ***iteration***, a conditional loop. Naming: giving names to a specific memory location holding data or holding a step. This is just a "convenience" to have. We do not add any new instructions by having the capacity to define “names” for memory locations. “Naming” is not a instruction for the agent, it’s just a convenience to us. Naming makes code (at this point) easier to read and easier to change. #define counter m[30] // name a memory location mov 1000 counter loop: // name a instruction pointer location sub counter 1 (if not-zero) jmp-to loop One-level subroutine: Suppose there’s a series of steps you need to execute frequently. You can store the steps in a named position in memory and then jump to that position when you need to execute them (call). At the end of the sequence you'll need to return to the point of calling to continue execution. With this mechanism, you’re creating new instructions (subroutines) by composing core instructions. Implementation: (no new concepts required) Store the current Instruction Pointer in a predefined memory position jump to the subroutine at the end of the subroutine, you retrieve the Instruction Pointer from the predefined memory location, effectively jumping back to the following instruction of the original call Problem with the one-level implementation: You cannot call another subroutine from a subroutine. If you do, you'll overwrite the returning address (global variable), so you cannot nest calls. To have a better Implementation for subroutines: You need a STACK Stack: You define a memory space to work as a "stack", you can “push” values on the stack, and also “pop” the last “pushed” value. To implement a stack you'll need a Stack Pointer (similar to the Instruction Pointer) which points to the actual “head” of the stack. When you “push” a value, the stack pointer decrements and you store the value. When you “pop”, you get the value at the actual Stack Pointer and then the Stack Pointer is incremented. Subroutines Now that we have a stack we can implement proper subroutines allowing nested calls. The implementation is similar, but instead of storing the Instruction Pointer in a predefined memory position, we "push" the value of the IP in the stack. At the end of the subroutine, we just “pop” the value from the stack, effectively jumping back to the instruction after the original call. This implementation, having a “stack” allows calling a subroutine from another subroutine. With this implementation we can create several levels of abstraction when defining new instructions as subroutines, by using core instructions or other subroutines as building blocks. Recursion: What happens when a subroutine calls itself?. This is called "recursion". Problem: Overwriting the local intermediate results a subroutine can be storing in memory. Since you are calling/reusing the same steps, if the intermediate result are stored in predefined memory locations (global variables) they will be overwritten on the nested calls. Solution: To allow recursion, subroutines should store local intermediate results in the stack, therefore, on each recursive call (direct or indirect) the intermediate results are stored in different memory locations.

...

到达递归之后，我们就停在这里。

结论:

在冯·诺依曼架构中，“迭代”显然是一个比“递归”更简单/基本的概念。我们有一种形式的“迭代”在第7级，而“递归”在概念层次的第14级。

在机器代码中迭代总是更快，因为它意味着更少的指令，因此更少的CPU周期。

哪个“更好”?

在处理简单的、顺序的数据结构时，应该使用“迭代”，而在任何地方都可以使用“简单循环”。 当你需要处理递归数据结构(我喜欢称它们为“分形数据结构”)时，或者递归解决方案明显更“优雅”时，你应该使用“递归”。

建议:使用最好的工具，但要了解每个工具的内部工作原理，以便做出明智的选择。

最后，请注意，您有很多机会使用递归。你到处都有递归数据结构，你现在看到的是:DOM中支持你读取内容的部分是RDS, JSON表达式是RDS，计算机中的分层文件系统也是RDS，即:你有一个根目录，包含文件和目录，每个目录包含文件和目录，每个目录包含文件和目录……

函数式编程更多的是关于“是什么”而不是“如何”。

语言实现者会找到一种方法来优化代码在底层的工作方式，如果我们不试图让它比它需要的更优化的话。递归也可以在支持尾部调用优化的语言中进行优化。

从程序员的角度来看，更重要的是可读性和可维护性，而不是首先进行优化。再次强调，“过早优化是万恶之源”。

尾递归和循环一样快。许多函数式语言都实现了尾部递归。

从理论上讲，两者是一样的。 具有相同O()复杂度的递归和循环将以相同的理论速度工作，但当然，实际速度取决于语言、编译器和处理器。 数幂例可用O(ln(n))迭代编码:

  int power(int t, int k) {
  int res = 1;
  while (k) {
    if (k & 1) res *= t;
    t *= t;
    k >>= 1;
  }
  return res;
  }