MySQL connection with mysql2 in Node.js - Performance & Optimization

Performance: MySQL connection with mysql2

MEDIUM IMPACT

This affects the initial page or API response load time by how quickly the database connection is established and queries are executed.

Connecting to MySQL and running queries in a Node.js app

Node.js

import mysql from 'mysql2/promise';
const pool = mysql.createPool({host: 'localhost', user: 'root', database: 'test', waitForConnections: true, connectionLimit: 10});
async function getUsers() {
  const [rows] = await pool.query('SELECT * FROM users');
  return rows;
}

Reuses connections from a pool asynchronously, reducing connection overhead and avoiding blocking.

📈 Performance GainReduces connection overhead by up to 90%, non-blocking queries improve throughput and lower latency

Connecting to MySQL and running queries in a Node.js app

Node.js

const mysql = require('mysql2');
const connection = mysql.createConnection({host: 'localhost', user: 'root', database: 'test'});
connection.query('SELECT * FROM users', (err, results) => {
  if (err) throw err;
  console.log(results);
});
connection.end();

Creates a new connection for every query, blocking the event loop and causing delays under load.

📉 Performance CostBlocks event loop during connection setup, triggers multiple TCP handshakes, increases response time by 100-200ms per query

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Single connection per query	N/A	N/A	N/A	[X] Bad
Connection pool with async queries	N/A	N/A	N/A	[OK] Good

Rendering Pipeline

Database connection and query execution happen before the server sends the response, affecting how fast the browser receives content.

→Server Processing

→Network Request

→First Byte Time

⚠️ BottleneckConnection setup and synchronous query execution block server event loop

Core Web Vital Affected

LCP

This affects the initial page or API response load time by how quickly the database connection is established and queries are executed.

Optimization Tips

1Always use connection pooling to reuse MySQL connections.

2Use async/await queries to avoid blocking the Node.js event loop.

3Avoid creating a new connection for every query to reduce latency.

Performance Quiz - 3 Questions

What is the main performance benefit of using a connection pool with mysql2 in Node.js?

A It compresses the database responses to save bandwidth

B It automatically caches query results in the browser

C Reusing existing connections reduces connection overhead and latency

D It prevents SQL injection attacks

DevTools: Network

How to check: Open DevTools Network panel, observe Time to First Byte (TTFB) for API calls that query MySQL

What to look for: High TTFB indicates slow database response; lower TTFB with pooling means better performance

Practice

1. What is the main purpose of the mysql2 package in Node.js?

easy

A. To create web servers

B. To connect and interact with MySQL databases

C. To style HTML pages

D. To manage file uploads

Solution

1. Step 1: Understand the role of mysql2

   The mysql2 package is designed to help Node.js applications connect to and communicate with MySQL databases.

2. Step 2: Compare with other options

   Options B, C, and D relate to other tasks like web servers, styling, or file uploads, which are not the purpose of mysql2.

3. Final Answer:

   To connect and interact with MySQL databases -> Option B

4. Quick Check:

   mysql2 = MySQL connection tool [OK]

Hint: Remember mysql2 is for database connection only [OK]

Common Mistakes:

• Confusing mysql2 with web server packages
• Thinking mysql2 styles web pages
• Assuming mysql2 handles file uploads

2. Which of the following is the correct way to create a connection using mysql2 in Node.js?

easy

A. const connection = mysql2.newConnection('localhost', 'root', 'pass');

B. const connection = mysql2.connect({host: 'localhost', user: 'root'});

C. const connection = mysql2.createConnection({host: 'localhost', user: 'root', password: 'pass', database: 'test'});

D. const connection = mysql2.open({host: 'localhost', user: 'root', password: 'pass'});

Solution

1. Step 1: Recall mysql2 connection syntax

   The correct method to create a connection is createConnection with an object containing host, user, password, and database.

2. Step 2: Check each option

   const connection = mysql2.createConnection({host: 'localhost', user: 'root', password: 'pass', database: 'test'}); uses createConnection with all required fields. Options A, B, and D use incorrect method names or missing parameters.

3. Final Answer:

   const connection = mysql2.createConnection({host: 'localhost', user: 'root', password: 'pass', database: 'test'}); -> Option C

4. Quick Check:

   Use createConnection with config object [OK]

Hint: Use createConnection with full config object [OK]

Common Mistakes:

• Using wrong method names like connect or open
• Omitting required fields like password or database
• Passing parameters as separate arguments instead of an object

3. Given the code below, what will be logged if the connection is successful?

const mysql = require('mysql2');
const connection = mysql.createConnection({host: 'localhost', user: 'root', password: 'pass', database: 'test'});
connection.connect(err => {
  if (err) {
    console.log('Connection failed');
  } else {
    console.log('Connected successfully');
  }
});

medium

A. No output

B. Connection failed

C. SyntaxError

D. Connected successfully

Solution

1. Step 1: Understand the connect callback

   The callback checks if there is an error. If no error, it logs 'Connected successfully'.

2. Step 2: Given connection is successful

   Since the connection is successful, err is null, so the else block runs.

3. Final Answer:

   Connected successfully -> Option D

4. Quick Check:

   Successful connection logs success message [OK]

Hint: No error means success message logs [OK]

Common Mistakes:

• Assuming error logs even on success
• Confusing callback parameters
• Expecting no output without callback

4. Identify the error in this code snippet for connecting to MySQL using mysql2:

const mysql = require('mysql2');
const connection = mysql.createConnection({host: 'localhost', user: 'root', password: 'pass'});
connection.connect(err => {
  if (err) throw err;
  console.log('Connected!');
});
connection.end();

medium

A. Using connection.end() before connect callback

B. No error, code is correct

C. Incorrect method createConnection instead of connect

D. Missing database name in connection config

Solution

1. Step 1: Check connection config

   While database name is missing, mysql2 allows connection without specifying database, so not a fatal error here.

2. Step 2: Analyze connection.end() placement

   connection.end() is called immediately after connect(), which may close connection before it is established or query runs.

3. Final Answer:

   Using connection.end() before connect callback -> Option A

4. Quick Check:

   Close connection only after queries finish [OK]

Hint: Call connection.end() after queries complete [OK]

Common Mistakes:

• Calling connection.end() too early
• Assuming database is always required
• Confusing createConnection with connect method

5. You want to run a query to select all users from a MySQL database using mysql2. Which code snippet correctly handles the connection, query, and closing the connection?

hard

A. const mysql = require('mysql2');
const conn = mysql.createConnection({host:'localhost', user:'root', password:'pass', database:'test'});
conn.connect(err => {
if (err) throw err;
conn.query('SELECT * FROM users', (err, results) => {
if (err) throw err;
console.log(results);
conn.end();
});
});

B. const mysql = require('mysql2');
const conn = mysql.createConnection({host:'localhost', user:'root', password:'pass', database:'test'});
conn.query('SELECT * FROM users', (err, results) => {
if (err) throw err;
console.log(results);
});
conn.end();

C. const mysql = require('mysql2');
const conn = mysql.createConnection({host:'localhost', user:'root', password:'pass', database:'test'});
conn.end();
conn.query('SELECT * FROM users', (err, results) => {
if (err) throw err;
console.log(results);
});

D. const mysql = require('mysql2');
const conn = mysql.createConnection({host:'localhost', user:'root', password:'pass'});
conn.query('SELECT * FROM users', (err, results) => {
if (err) throw err;
console.log(results);
conn.end();
});

Solution

1. Step 1: Properly connect before querying

   const mysql = require('mysql2'); const conn = mysql.createConnection({host:'localhost', user:'root', password:'pass', database:'test'}); conn.connect(err => { if (err) throw err; conn.query('SELECT * FROM users', (err, results) => { if (err) throw err; console.log(results); conn.end(); }); }); calls connect first, ensuring connection is ready before running the query.

2. Step 2: Close connection after query completes

   const mysql = require('mysql2'); const conn = mysql.createConnection({host:'localhost', user:'root', password:'pass', database:'test'}); conn.connect(err => { if (err) throw err; conn.query('SELECT * FROM users', (err, results) => { if (err) throw err; console.log(results); conn.end(); }); }); calls conn.end() inside the query callback, so connection closes only after query finishes.

3. Step 3: Check other options

   const mysql = require('mysql2'); const conn = mysql.createConnection({host:'localhost', user:'root', password:'pass', database:'test'}); conn.query('SELECT * FROM users', (err, results) => { if (err) throw err; console.log(results); }); conn.end(); calls conn.end() immediately after query, which may close connection too soon. const mysql = require('mysql2'); const conn = mysql.createConnection({host:'localhost', user:'root', password:'pass', database:'test'}); conn.end(); conn.query('SELECT * FROM users', (err, results) => { if (err) throw err; console.log(results); }); closes connection before query. const mysql = require('mysql2'); const conn = mysql.createConnection({host:'localhost', user:'root', password:'pass'}); conn.query('SELECT * FROM users', (err, results) => { if (err) throw err; console.log(results); conn.end(); }); misses database in config.

4. Final Answer:

   Correctly connects, queries, and closes connection in proper sequence using nested callbacks -> Option A

5. Quick Check:

   Connect first, query next, then close connection [OK]

Hint: Connect first, query inside callback, then close connection [OK]

Common Mistakes:

• Closing connection before query finishes
• Not waiting for connect callback before querying
• Omitting database in connection config