Password hashing with bcrypt in Node.js - Performance & Optimization

Performance: Password hashing with bcrypt

MEDIUM IMPACT

This affects server response time during user authentication and registration due to CPU-intensive hashing.

Hashing user passwords securely during signup

Node.js

const bcrypt = require('bcrypt');

async function hashPassword(password) {
  const saltRounds = 12; // recommended secure level
  return await bcrypt.hash(password, saltRounds);
}

Higher salt rounds increase CPU work, making hashes slower but much more secure.

📈 Performance Gainstrong security with acceptable CPU cost; prevents brute force attacks

Hashing user passwords securely during signup

Node.js

const bcrypt = require('bcrypt');

async function hashPassword(password) {
  const saltRounds = 4; // very low
  return await bcrypt.hash(password, saltRounds);
}

Using very low salt rounds weakens security and may encourage faster but unsafe hashing.

📉 Performance Costfast hashing but insecure, risking data breaches

Performance Comparison

Pattern	CPU Load	Event Loop Blocking	Response Delay	Verdict
Low salt rounds (e.g., 4)	Low CPU	No blocking	Fast response	[!] OK but insecure
Recommended salt rounds (e.g., 12)	High CPU	No blocking if async	Moderate delay (~100ms)	[OK] Secure and performant
Synchronous bcrypt calls	High CPU	Blocks event loop	Delays all requests	[X] Bad for server responsiveness

Rendering Pipeline

bcrypt hashing runs on the server CPU and does not affect browser rendering pipeline directly but impacts server response time.

→Server CPU processing

→Response time

⚠️ BottleneckCPU-intensive hashing delays server response

Optimization Tips

1Use asynchronous bcrypt methods to avoid blocking the Node.js event loop.

2Balance salt rounds to ensure strong security without excessive CPU delay.

3Avoid synchronous bcrypt calls in production to keep server responsive.

Performance Quiz - 3 Questions

What is the main performance impact of using bcrypt with high salt rounds?

A Increased network bandwidth usage

B Increased browser rendering time

C Increased CPU usage causing slower server responses

D Increased database query time

DevTools: Node.js Profiler or Chrome DevTools Performance panel (remote debugging)

How to check: Record CPU profile during login/signup requests; look for bcrypt hashing functions duration and event loop blocking

What to look for: Long CPU tasks blocking event loop indicate synchronous bcrypt usage; async usage shows shorter blocking times

Practice

1. What is the main purpose of using bcrypt in a Node.js application?

easy

A. To securely hash user passwords before storing them

B. To encrypt user data for faster retrieval

C. To compress files on the server

D. To generate random user IDs

Solution

1. Step 1: Understand bcrypt's role

   Bcrypt is designed to hash passwords securely, making them hard to reverse.

2. Step 2: Identify the correct purpose

   Encrypting data or compressing files are not bcrypt's functions; it focuses on password hashing.

3. Final Answer:

   To securely hash user passwords before storing them -> Option A

4. Quick Check:

   Password hashing = Secure storage [OK]

Hint: Bcrypt is for password security, not encryption or compression [OK]

Common Mistakes:

• Confusing hashing with encryption
• Thinking bcrypt compresses data
• Assuming bcrypt generates IDs

2. Which of the following is the correct way to hash a password asynchronously using bcrypt in Node.js?

easy

A. const hashed = await bcrypt.hash(password, 10);

B. const hashed = bcrypt.hashSync(password, 10);

C. const hashed = bcrypt.compare(password, 10);

D. const hashed = bcrypt.hash(password);

Solution

1. Step 1: Identify asynchronous hashing syntax

   Bcrypt's async hash function requires await and two arguments: password and salt rounds.

2. Step 2: Check each option

   hashSync uses the synchronous method, compare is for verification not hashing, and the hash call misses salt rounds.

3. Final Answer:

   const hashed = await bcrypt.hash(password, 10); -> Option A

4. Quick Check:

   Async hash needs await and salt rounds [OK]

Hint: Async bcrypt hash needs await and salt rounds [OK]

Common Mistakes:

• Using hashSync instead of async hash
• Calling compare instead of hash
• Omitting salt rounds argument

3. What will the following code output if the password matches the hash?

const bcrypt = require('bcrypt');

async function check() {
  const password = 'secret123';
  const hash = await bcrypt.hash(password, 10);
  const result = await bcrypt.compare('secret123', hash);
  console.log(result);
}
check();

medium

A. false

B. true

C. undefined

D. Error

Solution

1. Step 1: Understand bcrypt.compare behavior

   It returns true if the plain password matches the hashed password.

2. Step 2: Analyze the code flow

   The password 'secret123' is hashed and then compared with the same password, so result is true.

3. Final Answer:

   true -> Option B

4. Quick Check:

   Matching password returns true [OK]

Hint: Compare returns true if passwords match [OK]

Common Mistakes:

• Expecting false for matching passwords
• Confusing compare with hash
• Ignoring async/await in code

4. Identify the error in this bcrypt usage:

const bcrypt = require('bcrypt');

async function verify() {
  const password = 'mypassword';
  const hash = bcrypt.hash(password, 10);
  const match = await bcrypt.compare(password, hash);
  console.log(match);
}
verify();

medium

A. Incorrect salt rounds value

B. Using compare instead of hash to create hash

C. Password variable is not defined

D. Missing await before bcrypt.hash causing hash to be a Promise

Solution

1. Step 1: Check bcrypt.hash usage

   Bcrypt.hash is async and returns a Promise, so it needs await to get the hashed string.

2. Step 2: Identify the error impact

   Without await, hash is a Promise, causing compare to fail or behave unexpectedly.

3. Final Answer:

   Missing await before bcrypt.hash causing hash to be a Promise -> Option D

4. Quick Check:

   Async hash needs await [OK]

Hint: Always await async bcrypt.hash calls [OK]

Common Mistakes:

• Forgetting await on async functions
• Confusing compare with hash
• Using invalid salt rounds

5. You want to securely store user passwords and verify them later. Which approach correctly combines hashing and verification using bcrypt in an async function?

hard

A. Hash password synchronously with bcrypt.hashSync(password, 12) and verify asynchronously with await bcrypt.compare(input, storedHash)

B. Store the plain password and verify by hashing input with bcrypt.hashSync(input, 12) and comparing strings

C. Hash the password with await bcrypt.hash(password, 12) and verify with await bcrypt.compare(input, storedHash)

D. Encrypt password with bcrypt.encrypt(password) and decrypt for verification

Solution

1. Step 1: Choose secure async hashing and verification

   Using async bcrypt.hash with salt rounds (12) and async bcrypt.compare is best practice.

2. Step 2: Evaluate other options

   Storing plain passwords and hashing input for string comparison is insecure, mixing sync hashing with async verification is inconsistent, and bcrypt has no encrypt/decrypt methods.

3. Final Answer:

   Hash the password with await bcrypt.hash(password, 12) and verify with await bcrypt.compare(input, storedHash) -> Option C

4. Quick Check:

   Async hash and compare with salt rounds = secure [OK]

Hint: Use async hash and compare with salt rounds for security [OK]

Common Mistakes:

• Storing plain passwords
• Mixing sync and async bcrypt calls
• Assuming bcrypt can encrypt/decrypt