Scaling Writes medium
You need to import 1 million rows into a SQL database. Which method is fastest?
- A Using an ORM loop.
- B Sending 1 million individual INSERT statements.
- C Using a dedicated bulk load command (like `COPY` in Postgres or `LOAD DATA` in MySQL) to stream the CSV directly.
- D Inserting into a temporary table first.
Answer: C. Using a dedicated bulk load command (like `COPY` in Postgres or `LOAD DATA` in MySQL) to stream the CSV directly.
Bulk commands bypass the SQL parser overhead for every row and often optimize the transaction logging, resulting in orders-of-magnitude faster ingestion.
One system design question a day, with spaced repetition so the ones you miss come back.
Get the appRelated questions
- What does the 'Atomicity' property in a database transaction guarantee regarding writes?
- Your database is struggling with write traffic. You decide to 'Scale Up' (Vertical Scaling) by buying a bigger server. What is the eventual hard limit of this strategy?
- A developer sets up a 'Fire-and-Forget' write pattern (sending data without waiting for a database confirmation) to speed up the app. What is the major risk?
- Why is inserting 1,000 rows in a single 'Batch' query faster than executing 1,000 separate `INSERT` queries?
- In the Raft consensus algorithm, what mechanism prevents a 'Split Vote' (where no leader gets a majority) from stalling the cluster indefinitely?
- Your 'Logs' table has 10 billion rows and writes are getting slow. You barely access logs older than 1 year. What is the simplest strategy to improve performance?