Disk structure and access time in DBMS Theory - Step-by-Step Execution

Concept Flow - Disk structure and access time

Disk Structure

↓

Platters & Surfaces

↓

Tracks on Surfaces

↓

Sectors in Tracks

↓

Blocks (Sectors grouped)

↓

Access Time Components

↓

Seek Time + Rotational Delay + Transfer Time

Disk data is organized in platters with tracks and sectors; accessing data involves seek time, rotational delay, and transfer time.

Execution Sample

DBMS Theory

Access disk block:
1. Move head to track (seek)
2. Wait for sector (rotation)
3. Read data (transfer)

This sequence shows the steps to access data on a disk block.

Analysis Table

Step	Action	Details	Time Taken (ms)	Cumulative Time (ms)
1	Seek	Move head to correct track	8	8
2	Rotational Delay	Wait for sector under head	4	12
3	Transfer	Read data from sector	1	13
4	End	Data block accessed	-	13

💡 Disk block accessed after seek, rotation, and transfer times.

State Tracker

Variable	Start	After Seek	After Rotation	After Transfer	Final
Head Position	Track 0	Track 120	Track 120	Track 120	Track 120
Sector Position	Sector 0	Sector 0	Sector 45	Sector 45	Sector 45
Data Read	No	No	No	Yes	Yes
Elapsed Time (ms)	0	8	12	13	13

Key Insights - 3 Insights

Why does seek time take longer than rotational delay?

Seek time involves physically moving the read/write head to the correct track, which is slower than waiting for the disk to spin to the right sector (rotational delay), as shown in execution_table steps 1 and 2.

Is transfer time always the shortest part of access time?

Yes, transfer time is usually shortest because it is the time to read data once the head is positioned, as seen in execution_table step 3.

Why do we need to wait for rotational delay after seek?

After moving the head to the track, the disk must spin until the desired sector is under the head, causing rotational delay (step 2 in execution_table).

Visual Quiz - 3 Questions

Look at the execution_table, what is the cumulative time after the seek step?

A 4 ms

B 8 ms

C 12 ms

D 13 ms

💡 Hint

Check the 'Cumulative Time (ms)' column at step 1 in execution_table.

At which step does the data actually get read from the disk?

A Step 1 - Seek

B Step 2 - Rotational Delay

C Step 3 - Transfer

D Step 4 - End

💡 Hint

Refer to the 'Action' and 'Details' columns in execution_table for when data is read.

If the seek time increases, which variable in variable_tracker changes accordingly?

A Head Position

B Data Read

C Sector Position

D Elapsed Time

💡 Hint

Look at 'Head Position' and 'Elapsed Time' changes after seek in variable_tracker.

Concept Snapshot

Disk data is stored on spinning platters divided into tracks and sectors.
Accessing data involves three main times:
- Seek time: moving the head to the track
- Rotational delay: waiting for the sector to rotate under the head
- Transfer time: reading the data
Total access time = seek + rotation + transfer.

Full Transcript

Disk structure consists of platters with multiple surfaces. Each surface has concentric tracks, and each track is divided into sectors. Data is stored in these sectors grouped as blocks. To access data, the disk head moves to the correct track (seek time), waits for the disk to spin to the right sector (rotational delay), and then reads the data (transfer time). Seek time is usually the longest because it involves physical movement. Rotational delay depends on disk speed, and transfer time is the shortest. The total access time is the sum of these three components.