---
title: "Process vs thread; multithreading advantages"
subject: "Operating System"
chapter: 2
key: "semester_6/operating_system:process-thread-multithreading"
source: https://www.bctengineer.com/q/semester_6/operating_system/process-thread-multithreading
site: BCT Engineering
---

# Process vs thread; multithreading advantages

Operating System · Chapter 2: Process Management

- Asked in: 2072 Asoj, 2+2 marks
- Video: [L-1.11: Process Vs Threads in Operating System](https://www.youtube.com/watch?v=ITc09gOrqZk) — Gate Smashers
- Answer checked by Claude Opus 5.5 (high effort) on 2026-10-14
- Page: https://www.bctengineer.com/q/semester_6/operating_system/process-thread-multithreading
- Whole chapter: https://www.bctengineer.com/md/semester_6/operating_system/chapter-2

## Question

a) Differentiate between process and thread. Explain the advantages of multithreading.

## Short answer

A process is a heavyweight entity with its own address space, while a thread is a lightweight unit sharing the process's resources. Multithreading improves responsiveness, resource sharing, economy, multiprocessor utilization, and simplifies concurrent programming.

## Answer

#### Process vs thread

A **process** is a program in execution with its own address space and resources. A **thread** is a lightweight unit of execution within a process; threads of one process share its code, data and open files but have their own program counter, registers and stack.

| Basis | Process | Thread |
|---|---|---|
| Weight | Heavyweight | Lightweight |
| Address space | Separate for each process | Shared by threads of the same process |
| Creation / switching | Slow, costly | Fast, cheap |
| Communication | Needs IPC (pipes, messages) | Directly through shared memory |
| Protection | Isolated from other processes | No protection between threads |
| Failure | One process crash does not affect others | A faulty thread can kill the whole process |

#### Advantages of multithreading

- **Responsiveness**: the program continues (e.g. UI) while one thread is blocked or doing a long task.
- **Resource sharing**: threads share memory and files, so no special IPC is needed.
- **Economy**: creating and switching threads costs much less than processes.
- **Better use of multiprocessors**: threads run in parallel on different CPUs (scalability).
- **Simpler program structure** for concurrent tasks such as a web server serving many clients.

## Check yourself

The answer's key points as multiple-choice questions, with the correct option and why.

1. Which items do threads of the same process share, and which are private?
   A. Share the stack and registers; private code and data
   B. Share code, data and open files; private program counter, registers and stack
   C. Share nothing
   D. Share the program counter; private code
   Answer: B. Threads share the address space and resources of their process but each has its own PC, registers and stack. (Key point: What threads share)

2. What happens if a thread misbehaves, compared with a process?
   A. Only that thread is affected, as it is isolated
   B. A faulty thread can kill the whole process, while one process crash does not affect others
   C. Nothing, threads are protected from each other
   D. Other processes crash as well
   Answer: B. Threads have no protection between them, whereas processes are isolated from one another. (Key point: Process vs thread failure)

3. Why does multithreading improve responsiveness?
   A. The program can continue (e.g. the UI) while another thread is blocked or doing a long task
   B. It eliminates all I/O
   C. It increases the quantum
   D. It gives each thread a separate address space
   Answer: A. If one thread blocks, the others keep running, so the application stays responsive. (Key point: Multithreading advantage)

## Related in Operating System

- [What is process; process vs thread](https://www.bctengineer.com/question.md?key=semester_6%2Foperating_system%3Aprocess-vs-thread-define) — Operating System, chapter 2
- [Process vs thread; context switching](https://www.bctengineer.com/question.md?key=semester_6%2Foperating_system%3Athread-context-switching) — Operating System, chapter 2
- [Process vs thread; user and kernel threads](https://www.bctengineer.com/question.md?key=semester_6%2Foperating_system%3Aprocess-vs-thread-user-kernel-threads) — Operating System, chapter 2
- [Preemptive vs non-preemptive; process states](https://www.bctengineer.com/question.md?key=semester_6%2Foperating_system%3Apreemptive-nonpreemptive-process-states) — Operating System, chapter 2

## Related in other subjects

- [Process vs thread and task states](https://www.bctengineer.com/question.md?key=semester_6%2Fembedded_system%3Aprocess-thread-and-task-states) — Embedded System, chapter 6
- [Thread, multithreading and necessity](https://www.bctengineer.com/question.md?key=semester_6%2Fembedded_system%3Amultithreading-concept) — Embedded System, chapter 6
- [Process versus thread differences](https://www.bctengineer.com/question.md?key=semester_6%2Fembedded_system%3Aprocess-vs-thread) — Embedded System, chapter 6, asked 4×
- [Instruction, thread, process level parallelism](https://www.bctengineer.com/question.md?key=semester_4%2Fmicroprocessor%3Ainstruction-thread-process-parallelism) — Microprocessor, chapter 6