如果等待Promise.all([task1()， task2()]);“task1()”和“task2()”将并行运行，并等待两个promise都完成(解决或拒绝)。而在

const result1 = await t1;
const result2 = await t2;

T2将只在t1完成执行(已被解析或拒绝)后运行。t1和t2都不是平行的。

你可以自己查一下。

在这个小提琴中，我运行了一个测试来演示await的阻塞性质，而不是Promise。所有这些都将开始所有的承诺，当一个在等待的时候，它将与其他的一起继续。

注意: 这个答案只涵盖了await in series和Promise.all之间的时间差异。一定要阅读@mikep的全面回答，它还涵盖了错误处理中更重要的差异。

---

为了回答这个问题，我将使用一些示例方法:

Res (ms)是一个接受毫秒整数的函数，并返回一个承诺，该承诺在该毫秒后解析。 Rej (ms)是一个函数，它接受一个毫秒的整数，并返回一个承诺，该承诺在这个毫秒之后被拒绝。

调用res启动定时器。使用的承诺。所有等待少量延迟的问题将在所有延迟结束后解决，但请记住它们是同时执行的:

示例# 1

const data = await Promise.all([res(3000), res(2000), res(1000)])
//                              ^^^^^^^^^  ^^^^^^^^^  ^^^^^^^^^
//                               delay 1    delay 2    delay 3
//
// ms ------1---------2---------3
// =============================O delay 1
// ===================O           delay 2
// =========O                     delay 3
//
// =============================O Promise.all

异步函数示例(){ const start = Date.now() 令I = 0 函数res(n) { Const id = ++i 返回新的承诺((resolve, reject) => { setTimeout(() => { 解决() console.log(' res #${id}在${n}毫秒后调用'，Date.now() - start) }, n) }） } const data = await Promise.all([res(3000)， res(2000)， res(1000)]) console.log('的承诺。all finished '， Date.now() - start) } 例()

这意味着承诺。3秒后，所有问题将与来自内部承诺的数据一起解决。

但是,承诺。所有这些都有“快速失败”的行为:

例# 2

const data = await Promise.all([res(3000), res(2000), rej(1000)])
//                              ^^^^^^^^^  ^^^^^^^^^  ^^^^^^^^^
//                               delay 1    delay 2    delay 3
//
// ms ------1---------2---------3
// =============================O delay 1
// ===================O           delay 2
// =========X                     delay 3
//
// =========X                     Promise.all

async function example() { const start = Date.now() let i = 0 function res(n) { const id = ++i return new Promise((resolve, reject) => { setTimeout(() => { resolve() console.log(`res #${id} called after ${n} milliseconds`, Date.now() - start) }, n) }) } function rej(n) { const id = ++i return new Promise((resolve, reject) => { setTimeout(() => { reject() console.log(`rej #${id} called after ${n} milliseconds`, Date.now() - start) }, n) }) } try { const data = await Promise.all([res(3000), res(2000), rej(1000)]) } catch (error) { console.log(`Promise.all finished`, Date.now() - start) } } example()

如果你使用async-await来代替，你将不得不等待每个promise按顺序解析，这可能不那么有效:

示例# 3

const delay1 = res(3000)
const delay2 = res(2000)
const delay3 = rej(1000)

const data1 = await delay1
const data2 = await delay2
const data3 = await delay3

// ms ------1---------2---------3
// =============================O delay 1
// ===================O           delay 2
// =========X                     delay 3
//
// =============================X await

async function example() { const start = Date.now() let i = 0 function res(n) { const id = ++i return new Promise((resolve, reject) => { setTimeout(() => { resolve() console.log(`res #${id} called after ${n} milliseconds`, Date.now() - start) }, n) }) } function rej(n) { const id = ++i return new Promise((resolve, reject) => { setTimeout(() => { reject() console.log(`rej #${id} called after ${n} milliseconds`, Date.now() - start) }, n) }) } try { const delay1 = res(3000) const delay2 = res(2000) const delay3 = rej(1000) const data1 = await delay1 const data2 = await delay2 const data3 = await delay3 } catch (error) { console.log(`await finished`, Date.now() - start) } } example()

通常，使用Promise.all()以“异步”方式并行运行请求。使用await可以并行运行或被“同步”阻塞。

下面的Test1和test2函数显示await如何运行async或sync。

test3显示的Promise.all()是异步的。

Jsfiddle计时结果-打开浏览器控制台查看测试结果

同步行为。不并行运行，耗时~1800ms:

const test1 = async () => {
  const delay1 = await Promise.delay(600); //runs 1st
  const delay2 = await Promise.delay(600); //waits 600 for delay1 to run
  const delay3 = await Promise.delay(600); //waits 600 more for delay2 to run
};

异步行为。并行运行，约600ms:

const test2 = async () => {
  const delay1 = Promise.delay(600);
  const delay2 = Promise.delay(600);
  const delay3 = Promise.delay(600);
  const data1 = await delay1;
  const data2 = await delay2;
  const data3 = await delay3; //runs all delays simultaneously
}

异步行为。并行运行，耗时约600ms:

const test3 = async () => {
  await Promise.all([
  Promise.delay(600), 
  Promise.delay(600), 
  Promise.delay(600)]); //runs all delays simultaneously
};

TLDR;如果你正在使用Promise.all()，它也会“快速失败”——在任何包含的函数第一次失败时停止运行。

如果等待Promise.all([task1()， task2()]);“task1()”和“task2()”将并行运行，并等待两个promise都完成(解决或拒绝)。而在

const result1 = await t1;
const result2 = await t2;

T2将只在t1完成执行(已被解析或拒绝)后运行。t1和t2都不是平行的。

第一个区别——快速失败

I agree with @zzzzBov's answer, but the "fail fast" advantage of Promise.all is not the only difference. Some users in the comments have asked why using Promise.all is worth it when it's only faster in the negative scenario (when some task fails). And I ask, why not? If I have two independent async parallel tasks and the first one takes a very long time to resolve but the second is rejected in a very short time, why leave the user to wait for the longer call to finish to receive an error message? In real-life applications we must consider the negative scenario. But OK - in this first difference you can decide which alternative to use: Promise.all vs. multiple await.

第二个区别——错误处理

But when considering error handling, YOU MUST use Promise.all. It is not possible to correctly handle errors of async parallel tasks triggered with multiple awaits. In the negative scenario, you will always end with UnhandledPromiseRejectionWarning and PromiseRejectionHandledWarning, regardless of where you use try/ catch. That is why Promise.all was designed. Of course someone could say that we can suppress those errors using process.on('unhandledRejection', err => {}) and process.on('rejectionHandled', err => {}) but this is not good practice. I've found many examples on the internet that do not consider error handling for two or more independent async parallel tasks at all, or consider it but in the wrong way - just using try/ catch and hoping it will catch errors. It's almost impossible to find good practice in this.

总结

TL;DR:永远不要对两个或多个独立的异步并行任务使用多个await，因为您将无法正确处理错误。对于这个用例，总是使用Promise.all()。

Async/ await不是promise的替代品，它只是一种使用promise的漂亮方式。异步代码是用“同步风格”编写的，我们可以避免在承诺中使用多个then。

有些人说，当使用promise .all()时，我们不能单独处理任务错误，我们只能处理第一个被拒绝的承诺的错误(单独处理可以很有用，例如用于日志记录)。这不是问题——请参阅答案底部的“加法”标题。

例子

考虑这个异步任务…

const task = function(taskNum, seconds, negativeScenario) {
  return new Promise((resolve, reject) => {
    setTimeout(_ => {
      if (negativeScenario)
        reject(new Error('Task ' + taskNum + ' failed!'));
      else
        resolve('Task ' + taskNum + ' succeed!');
    }, seconds * 1000)
  });
};

当你在积极的情况下运行任务时，Promise和Promise之间没有区别。所有和多个等待。两个例子都以Task 1 succeed!任务2成功!5秒钟后。

// Promise.all alternative
const run = async function() {
  // tasks run immediately in parallel and wait for both results
  let [r1, r2] = await Promise.all([
    task(1, 5, false),
    task(2, 5, false)
  ]);
  console.log(r1 + ' ' + r2);
};
run();
// at 5th sec: Task 1 succeed! Task 2 succeed!

// multiple await alternative
const run = async function() {
  // tasks run immediately in parallel
  let t1 = task(1, 5, false);
  let t2 = task(2, 5, false);
  // wait for both results
  let r1 = await t1;
  let r2 = await t2;
  console.log(r1 + ' ' + r2);
};
run();
// at 5th sec: Task 1 succeed! Task 2 succeed!

但是，当第一个任务花了10秒并成功，第二个任务花了5秒但失败时，发出的错误是不同的。

// Promise.all alternative
const run = async function() {
  let [r1, r2] = await Promise.all([
    task(1, 10, false),
    task(2, 5, true)
  ]);
  console.log(r1 + ' ' + r2);
};
run();
// at 5th sec: UnhandledPromiseRejectionWarning: Error: Task 2 failed!

// multiple await alternative
const run = async function() {
  let t1 = task(1, 10, false);
  let t2 = task(2, 5, true);
  let r1 = await t1;
  let r2 = await t2;
  console.log(r1 + ' ' + r2);
};
run();
// at 5th sec: UnhandledPromiseRejectionWarning: Error: Task 2 failed!
// at 10th sec: PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 1)
// at 10th sec: UnhandledPromiseRejectionWarning: Error: Task 2 failed!

我们应该已经注意到，当并行使用多个等待时，我们正在做一些错误的事情。让我们试着处理错误:

// Promise.all alternative
const run = async function() {
  let [r1, r2] = await Promise.all([
    task(1, 10, false),
    task(2, 5, true)
  ]);
  console.log(r1 + ' ' + r2);
};
run().catch(err => { console.log('Caught error', err); });
// at 5th sec: Caught error Error: Task 2 failed!

如您所见，要成功地处理错误，我们只需要向运行函数添加一个捕获，并将带有捕获逻辑的代码添加到回调中。我们不需要在运行函数内部处理错误，因为异步函数会自动执行此操作——承诺拒绝任务函数会导致拒绝运行函数。

为了避免回调，我们可以使用“sync style”(async/ await + try/ catch) 尝试{等待运行();} catch(err) {} 但在这个例子中，这是不可能的，因为我们不能在主线程中使用await -它只能在异步函数中使用(因为没有人想阻塞主线程)。为了测试处理是否以“同步风格”工作，我们可以从另一个异步函数调用运行函数或使用IIFE(立即调用函数表达式:MDN):

(async function() { 
  try { 
    await run(); 
  } catch(err) { 
    console.log('Caught error', err); 
  }
})();

这是运行两个或多个异步并行任务并处理错误的唯一正确方法。你应该避免使用下面的例子。

不好的例子

// multiple await alternative
const run = async function() {
  let t1 = task(1, 10, false);
  let t2 = task(2, 5, true);
  let r1 = await t1;
  let r2 = await t2;
  console.log(r1 + ' ' + r2);
};

我们可以尝试用几种方法处理上面代码中的错误…

try { run(); } catch(err) { console.log('Caught error', err); };
// at 5th sec: UnhandledPromiseRejectionWarning: Error: Task 2 failed!
// at 10th sec: UnhandledPromiseRejectionWarning: Error: Task 2 failed!
// at 10th sec: PromiseRejectionHandledWarning: Promise rejection was handled 

…什么都没有被捕获，因为它处理同步代码，但运行是异步的。

run().catch(err => { console.log('Caught error', err); });
// at 5th sec: UnhandledPromiseRejectionWarning: Error: Task 2 failed!
// at 10th sec: Caught error Error: Task 2 failed!
// at 10th sec: PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 1)

．.． 嗯?我们首先看到任务2的错误没有被处理，后来它被捕获了。在主机中仍然充满误导和错误，这种方式仍然不可用。

(async function() { try { await run(); } catch(err) { console.log('Caught error', err); }; })();
// at 5th sec: UnhandledPromiseRejectionWarning: Error: Task 2 failed!
// at 10th sec: Caught error Error: Task 2 failed!
// at 10th sec: PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 1)

... the same as above. User @Qwerty in his deleted answer asked about this strange behaviour where an error seems to be caught but are also unhandled. We catch error the because run() is rejected on the line with the await keyword and can be caught using try/ catch when calling run(). We also get an unhandled error because we are calling an async task function synchronously (without the await keyword), and this task runs and fails outside the run() function. It is similar to when we are not able to handle errors by try/ catch when calling some sync function which calls setTimeout:

function test() {
  setTimeout(function() { 
    console.log(causesError); 
  }, 0);
};

try { 
  test(); 
} catch(e) { 
  /* this will never catch error */ 
}`.

另一个糟糕的例子:

const run = async function() {
  try {
    let t1 = task(1, 10, false);
    let t2 = task(2, 5, true);
    let r1 = await t1;
    let r2 = await t2;
  }
  catch (err) {
    return new Error(err);
  }
  console.log(r1 + ' ' + r2);
};
run().catch(err => { console.log('Caught error', err); });
// at 5th sec: UnhandledPromiseRejectionWarning: Error: Task 2 failed!
// at 10th sec: PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 1)

．.． “只有”两个错误(第三个错误是缺失的)，但什么都没有捕获。

附加(处理独立任务错误和首次失败错误)

const run = async function() {
  let [r1, r2] = await Promise.all([
    task(1, 10, true).catch(err => { console.log('Task 1 failed!'); throw err; }),
    task(2, 5, true).catch(err => { console.log('Task 2 failed!'); throw err; })
  ]);
  console.log(r1 + ' ' + r2);
};
run().catch(err => { console.log('Run failed (does not matter which task)!'); });
// at 5th sec: Task 2 failed!
// at 5th sec: Run failed (does not matter which task)!
// at 10th sec: Task 1 failed!

．.． 请注意，在这个例子中，我拒绝了两个任务，以更好地演示发生了什么(throw err用于触发最终错误)。