Creating promises in Javascript - Performance & Efficiency

Time Complexity: Creating promises

O(n)

Understanding Time Complexity

When we create promises in JavaScript, we want to know how the time to create and run them changes as we add more promises.

We ask: How does the work grow when we make many promises?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

const createPromises = (n) => {
  const promises = [];
  for (let i = 0; i < n; i++) {
    promises.push(new Promise((resolve) => {
      setTimeout(() => resolve(i), 100);
    }));
  }
  return Promise.all(promises);
};
    

This code creates an array of n promises that each resolve after a short delay, then waits for all to finish.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: The for loop creating n promises.
• How many times: Exactly n times, once per promise.

How Execution Grows With Input

Each promise is created one after another, so the work grows directly with n.

Input Size (n)	Approx. Operations
10	10 promise creations
100	100 promise creations
1000	1000 promise creations

Pattern observation: The work increases evenly as we add more promises.

Final Time Complexity

Time Complexity: O(n)

This means the time to create all promises grows in a straight line with the number of promises.

Common Mistake

[X] Wrong: "Creating many promises runs instantly and does not depend on how many there are."

[OK] Correct: Even though promises run asynchronously, creating each one takes time, so more promises mean more work upfront.

Interview Connect

Understanding how promise creation scales helps you write efficient asynchronous code and explain your reasoning clearly in interviews.

Self-Check

"What if we created promises inside a nested loop? How would the time complexity change?"

Practice

1. What does the resolve function do inside a JavaScript Promise?

easy

A. It pauses the promise execution.

B. It marks the promise as failed.

C. It marks the promise as successfully completed.

D. It cancels the promise.

Solution

1. Step 1: Understand the role of resolve in promises

   The resolve function is called when the asynchronous task finishes successfully.

2. Step 2: Differentiate from reject

   reject is used for failure, so resolve must mean success.

3. Final Answer:

   It marks the promise as successfully completed. -> Option C

4. Quick Check:

   resolve = success [OK]

Hint: Resolve means success, reject means failure [OK]

Common Mistakes:

• Confusing resolve with reject
• Thinking resolve cancels the promise
• Believing resolve pauses execution

2. Which of the following is the correct syntax to create a new Promise in JavaScript?

easy

A. new Promise(resolve, reject) => { }

B. Promise.new((resolve, reject) => { })

C. new Promise { resolve, reject => }

D. new Promise((resolve, reject) => { })

Solution

1. Step 1: Recall the Promise constructor syntax

   The Promise constructor takes a single function with two parameters: resolve and reject, wrapped in parentheses.

2. Step 2: Check each option for correct syntax

   new Promise((resolve, reject) => { }) correctly uses new Promise((resolve, reject) => { }). Others have syntax errors.

3. Final Answer:

   new Promise((resolve, reject) => { }) -> Option D

4. Quick Check:

   Promise syntax = new Promise((resolve, reject) => { }) [OK]

Hint: Promise needs a function with (resolve, reject) inside parentheses [OK]

Common Mistakes:

• Missing parentheses around parameters
• Using wrong keyword order
• Incorrect arrow function syntax

3. What will be the output of this code?

const p = new Promise((resolve, reject) => {
  resolve('Done');
});
p.then(result => console.log(result));

medium

A. Done

B. undefined

C. Error

D. Promise { <pending> }

Solution

1. Step 1: Understand promise resolution

   The promise calls resolve('Done'), so it completes successfully with value 'Done'.

2. Step 2: Check what then does

   then receives the resolved value and logs it, so 'Done' is printed.

3. Final Answer:

   Done -> Option A

4. Quick Check:

   Resolved value logged = Done [OK]

Hint: Resolve value appears in then callback [OK]

Common Mistakes:

• Expecting undefined instead of resolved value
• Confusing promise object with resolved output
• Thinking promise logs automatically

4. Find the error in this Promise creation code:

const p = new Promise(resolve, reject) => {
  resolve('Success');
};

medium

A. The reject function is never called.

B. Arrow function syntax is incorrect for Promise constructor.

C. Promise constructor missing the new keyword.

D. No error, code is correct.

Solution

1. Step 1: Check Promise constructor usage

   The Promise constructor requires a single function argument wrapped in parentheses.

2. Step 2: Identify arrow function syntax error

   The code uses new Promise(resolve, reject) => { } which is invalid syntax. It should be new Promise((resolve, reject) => { }).

3. Final Answer:

   Arrow function syntax is incorrect for Promise constructor. -> Option B

4. Quick Check:

   Arrow function must be inside parentheses [OK]

Hint: Promise needs one function argument wrapped in parentheses [OK]

Common Mistakes:

• Not wrapping parameters in parentheses
• Omitting new keyword (not in this case)
• Using wrong arrow function syntax

5. You want to create a Promise that waits 1 second and then resolves with 'Done'. Which code correctly does this?

hard

A. new Promise((resolve) => { setTimeout(() => resolve('Done'), 1000); })

B. new Promise(resolve => setTimeout(resolve('Done'), 1000))

C. new Promise((resolve, reject) => { resolve('Done'); setTimeout(() => {}, 1000); })

D. new Promise(() => { setTimeout(() => resolve('Done'), 1000); })

Solution

1. Step 1: Understand how to delay resolution

   Use setTimeout to delay calling resolve by 1000 ms (1 second).

2. Step 2: Check each option for correct usage

   new Promise((resolve) => { setTimeout(() => resolve('Done'), 1000); }) correctly passes a function to Promise and calls resolve('Done') inside setTimeout. new Promise(resolve => setTimeout(resolve('Done'), 1000)) calls resolve immediately. new Promise((resolve, reject) => { resolve('Done'); setTimeout(() => {}, 1000); }) resolves immediately and delays nothing. new Promise(() => { setTimeout(() => resolve('Done'), 1000); }) does not receive resolve parameter.

3. Final Answer:

   new Promise((resolve) => { setTimeout(() => resolve('Done'), 1000); }) -> Option A

4. Quick Check:

   Delay resolve with setTimeout inside Promise [OK]

Hint: Wrap resolve call inside setTimeout function [OK]

Common Mistakes:

• Calling resolve immediately instead of inside setTimeout
• Not passing resolve parameter
• Placing setTimeout outside Promise