Delay vs Thread.sleep in Kotlin - Hands-On Comparison

Delay vs Thread.sleep in Kotlin

📖 Scenario: You are building a simple Kotlin program to understand how to pause execution in two different ways: using Thread.sleep and delay from coroutines. This helps you see how blocking and non-blocking pauses work in real programs.

🎯 Goal: Create a Kotlin program that first pauses using Thread.sleep and then pauses using delay inside a coroutine. You will see the difference in how the program behaves.

📋 What You'll Learn

Create a main function

Use Thread.sleep to pause for 1000 milliseconds

Use delay to pause for 1000 milliseconds inside a coroutine

Print messages before and after each pause to observe the flow

💡 Why This Matters

🌍 Real World

Understanding blocking vs non-blocking pauses is important when writing apps that need to stay responsive, like games or user interfaces.

💼 Career

Many Kotlin jobs require knowledge of coroutines and how to manage delays without freezing the app, improving user experience.

1

Create the main function and print start message

Write a main function and inside it print "Program started".

Kotlin

fun main() {
    // Your code here
}

Hint

Use fun main() to create the main function and println to print the message.

2

Add Thread.sleep to pause for 1000 milliseconds

Inside the main function, after printing "Program started", add Thread.sleep(1000) to pause the program for 1000 milliseconds, then print "After Thread.sleep".

Kotlin

fun main() {
    println("Program started")
    // Your code here
}

Hint

Use Thread.sleep(1000) to pause for 1 second, then print the message after it.

3

Add coroutine with delay to pause without blocking

Import kotlinx.coroutines.*. Inside main, add runBlocking block. Inside it, print "Before delay", then call delay(1000), then print "After delay".

Kotlin

import kotlinx.coroutines.*

fun main() {
    println("Program started")
    Thread.sleep(1000)
    println("After Thread.sleep")
    // Your code here
}

Hint

Use runBlocking to start a coroutine in main. Inside it, use delay(1000) to pause without blocking the thread.

4

Print final message after coroutine block

After the runBlocking block in main, print "Program ended" to show the program finished.

Kotlin

import kotlinx.coroutines.*

fun main() {
    println("Program started")
    Thread.sleep(1000)
    println("After Thread.sleep")

    runBlocking {
        println("Before delay")
        delay(1000)
        println("After delay")
    }
    // Your code here
}

Hint

Print "Program ended" after the coroutine finishes to see the full flow.

Practice

1. What is the main difference between delay and Thread.sleep in Kotlin?

easy

A. Both delay and Thread.sleep block the thread in the same way.

B. delay pauses a coroutine without blocking the thread, while Thread.sleep blocks the thread.

C. delay blocks the thread, while Thread.sleep pauses a coroutine without blocking.

D. delay is used only for UI updates, Thread.sleep is for background tasks.

Solution

1. Step 1: Understand delay behavior

   delay suspends the coroutine but does not block the underlying thread, allowing other coroutines to run.

2. Step 2: Understand Thread.sleep behavior

   Thread.sleep blocks the entire thread, stopping all work on that thread until the sleep time ends.

3. Final Answer:

   delay pauses a coroutine without blocking the thread, while Thread.sleep blocks the thread. -> Option B

4. Quick Check:

   delay = non-blocking pause, Thread.sleep = blocking pause [OK]

Hint: delay suspends coroutines; Thread.sleep blocks threads [OK]

Common Mistakes:

• Thinking delay blocks the thread
• Confusing coroutine suspension with thread blocking
• Assuming both behave the same way

2. Which of the following is the correct way to use delay in a Kotlin coroutine?

easy

A. Thread.delay(1000)

B. Thread.sleep(1000)

C. delay.sleep(1000)

D. delay(1000)

Solution

1. Step 1: Recall delay syntax

   delay is a suspend function called with the time in milliseconds as an argument, e.g., delay(1000).

2. Step 2: Identify incorrect options

   Thread.delay and delay.sleep do not exist. Thread.sleep is a different blocking function.

3. Final Answer:

   delay(1000) -> Option D

4. Quick Check:

   Correct syntax for delay = delay(1000) [OK]

Hint: Use delay(milliseconds) inside coroutines only [OK]

Common Mistakes:

• Using Thread.delay instead of delay
• Confusing delay with Thread.sleep syntax
• Calling delay outside coroutine scope

3. What will be the output of this Kotlin coroutine code snippet?

import kotlinx.coroutines.*

fun main() = runBlocking {
    println("Start")
    delay(500)
    println("Middle")
    Thread.sleep(500)
    println("End")
}

medium

A. Start
Middle
End (with 1 second total delay)

B. Start
End
Middle (order switched)

C. Start
Middle
End (with 0.5 second total delay)

D. Start
End (missing Middle)

Solution

1. Step 1: Analyze the coroutine flow

   The program prints "Start", then suspends for 500ms using delay, then prints "Middle".

2. Step 2: Analyze the thread blocking

   After "Middle", Thread.sleep(500) blocks the thread for 500ms, then prints "End".

3. Final Answer:

   Start Middle End (with 1 second total delay) -> Option A

4. Quick Check:

   delay + Thread.sleep = total 1 second pause [OK]

Hint: delay suspends coroutine; Thread.sleep blocks thread sequentially [OK]

Common Mistakes:

• Assuming delay and Thread.sleep run in parallel
• Thinking delay blocks the thread
• Confusing output order

4. Identify the problem in this Kotlin coroutine code and choose the fix:

import kotlinx.coroutines.*

fun main() = runBlocking {
    println("Before sleep")
    Thread.sleep(1000)
    println("After sleep")
}

medium

A. Change Thread.sleep(1000) to Thread.delay(1000) for coroutine compatibility.

B. Add runBlocking inside the main function to fix the error.

C. Replace Thread.sleep(1000) with delay(1000) to avoid blocking the thread.

D. No problem; the code is correct as is.

Solution

1. Step 1: Identify blocking call in coroutine

   Thread.sleep(1000) blocks the thread, which is not recommended inside coroutines.

2. Step 2: Suggest coroutine-friendly alternative

   Use delay(1000) to suspend the coroutine without blocking the thread.

3. Final Answer:

   Replace Thread.sleep(1000) with delay(1000) to avoid blocking the thread. -> Option C

4. Quick Check:

   Use delay, not Thread.sleep, inside coroutines [OK]

Hint: Avoid Thread.sleep in coroutines; use delay instead [OK]

Common Mistakes:

• Using Thread.sleep inside coroutines
• Trying to use Thread.delay which doesn't exist
• Ignoring thread blocking effects

5. You want to run two tasks concurrently in Kotlin coroutines, each pausing for 1 second. Which approach uses delay correctly to avoid blocking threads and runs tasks concurrently?

fun main() = runBlocking {
    // Choose the correct code snippet
}

hard

A. launch { delay(1000); println("Task 1 done") }
launch { delay(1000); println("Task 2 done") }

B. launch { Thread.sleep(1000); println("Task 1 done") }
launch { Thread.sleep(1000); println("Task 2 done") }

C. Thread.sleep(1000); println("Task 1 done")
Thread.sleep(1000); println("Task 2 done")

D. delay(1000); println("Task 1 done")
delay(1000); println("Task 2 done")

Solution

1. Step 1: Understand concurrency with coroutines

   Using launch starts concurrent coroutines. Inside them, delay suspends without blocking threads.

2. Step 2: Analyze options for concurrency and blocking

   launch { delay(1000); println("Task 1 done") } launch { delay(1000); println("Task 2 done") } uses delay inside launch, enabling concurrency. launch { Thread.sleep(1000); println("Task 1 done") } launch { Thread.sleep(1000); println("Task 2 done") } blocks threads with Thread.sleep. Thread.sleep(1000); println("Task 1 done") Thread.sleep(1000); println("Task 2 done") blocks main thread sequentially. delay(1000); println("Task 1 done") delay(1000); println("Task 2 done") calls delay outside coroutine scope, causing error.

3. Final Answer:

   launch { delay(1000); println("Task 1 done") } launch { delay(1000); println("Task 2 done") } -> Option A

4. Quick Check:

   Use launch + delay for concurrent non-blocking tasks [OK]

Hint: Use launch with delay for concurrency, not Thread.sleep [OK]

Common Mistakes:

• Using Thread.sleep inside launch blocks threads
• Calling delay outside coroutine scope
• Running tasks sequentially blocking main thread