# Sequential I/O

Sequential I/O is a storage access pattern in which data is read or written in consecutive logical locations rather than at scattered locations.

Cloud concept. Updated 2026-10-29. Page: https://blowstack.com/tools/cloud-concepts-hub/sequential-io

> Sequential I/O commonly occurs when applications scan large files, stream media, write logs, or create backups. It typically emphasizes sustained throughput rather than small-operation latency, making it an important factor when selecting cost-effective storage.

Practice exams covering Sequential I/O: [SAA-C03 AWS Certified Solutions Architect - Associate](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate), [SAP-C03 AWS Certified Solutions Architect - Professional](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional).

## 6 key aspects of Sequential I/O

Sequential I/O favors consecutive access and sustained throughput, but economical storage choices depend on latency, access frequency, workload mixing, and end-to-end limits.

1. **Consecutive logical access**: Requests progress through adjacent logical offsets rather than jumping among scattered locations. This describes the application's access pattern, not a guarantee about physical data placement.
2. **Throughput-focused performance**: Large sequential workloads usually depend on sustained data transfer rates. Evaluate request size, IOPS, and latency together rather than using any single metric as a complete performance measure.
3. **Storage cost alignment**: Throughput-oriented HDD storage can be economical when sequential transfers dominate and latency requirements are relaxed. Compare total cost and sustained performance with SSD, file, and object storage alternatives.
4. **Buffering and read-ahead**: Batching transfers and prefetching upcoming data can reduce per-request overhead and keep storage busy. Tune these mechanisms carefully because unnecessary prefetching wastes bandwidth and buffered writes require durability controls.
5. **Mixed-workload effects**: Sequential scans can coexist with random lookups or compete with other readers and writers. Measure the combined workload because shared access can change both performance and the appropriate storage choice.
6. **End-to-end performance limits**: Storage throughput is only one constraint; instance bandwidth, network capacity, CPU processing, and burst credits may limit the application first. Test long enough to distinguish sustained performance from temporary bursts.

## Cloud services for Sequential I/O

Amazon S3 can hold durable source datasets and processing outputs, while Amazon EBS provides attached block storage for applications that need local file systems or block access. Choose EBS volume types according to the measured access pattern rather than assuming every scan requires SSD performance. When multiple compute nodes need shared, high-throughput file access, Amazon FSx for Lustre can provide a parallel processing layer integrated with S3. These services represent different access models, not mandatory components of one architecture; select the smallest combination that meets throughput, latency, durability, and cost requirements.

- **[Amazon S3](https://blowstack.com/tools/cloud-services-hub/amazon-s3)**: S3 supports large-object reads and writes for backups, media, and data processing, including parallel reads of object ranges. It provides object rather than block semantics, so request patterns, storage classes, retrieval charges, and transfer costs must be considered.

## Sequential I/O exam questions

Real practice exam questions on Sequential I/O, with the correct answer and its explanation.

### Question 1 (SAA-C03)

**Question:**

A video-processing company runs an application on an Amazon EC2 instance with a 512-GiB Amazon EBS General Purpose SSD (gp3) data volume. The volume has 3,000 IOPS and 125 MiB/s of throughput. The application writes large video files from beginning to end by using 1-MiB requests. A new processing pipeline must sustain 400 MiB/s of writes for several hours without relying on burst credits. Storage capacity will remain unchanged, and individual I/O latency is not important. The EC2 instance has sufficient EBS bandwidth, and there is no other traffic to the volume.

Which configuration will meet the requirement at the LOWEST ongoing EBS cost?

**Correct answer:** Keep the 512-GiB gp3 volume and 3,000 IOPS. Increase provisioned throughput to 400 MiB/s.

**Explanation:** Large sequential writes primarily require throughput. EBS SSD volumes account for I/O in units of up to 256 KiB, so each 1-MiB write consumes four I/O operations. At 400 writes per second, the workload requires approximately 1,600 IOPS, which is within the included 3,000 IOPS. Increasing only throughput meets the requirement without paying for unnecessary IOPS or a more expensive volume type.

### Question 2 (SAP-C03)

**Question:**

A scientific data-processing company runs an application on a single Amazon EC2 instance. The application repeatedly scans multi-terabyte instrument files from beginning to end, using 1 MiB reads and several outstanding requests. The application requires an attached block device with a local file system and cannot use an object-storage API or a network file system.

The data volume must provide 8 TiB of usable capacity and sustain at least 300 MiB/s of read throughput during processing campaigns that run continuously for several days. Millisecond-level variations in individual request latency are acceptable. The EC2 instance has sufficient dedicated EBS bandwidth, and the operating system is configured appropriately for large transfers. The boot volume is managed separately.

Which data-volume configuration meets these requirements at the LOWEST storage cost without depending on accumulated burst credits?

**Correct answer:** Use one 8 TiB EBS Throughput Optimized HDD (st1) volume.

**Explanation:** The large, ordered reads are well suited to throughput-oriented HDD storage. An st1 volume provides baseline throughput of 40 MiB/s per TiB, so an 8 TiB volume provides 320 MiB/s without relying on burst credits. This exceeds the 300 MiB/s requirement and costs less than the qualifying SSD configurations.

## Practice Sequential I/O in a full exam

Questions on Sequential I/O in each practice exam, with every answer option and an explanation for each:

- [SAA-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate): 2 questions
- [SAP-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional): 1 question

## What is Sequential I/O

Sequential I/O means reading or writing consecutive logical locations in a file, object, or block address space. An application scanning a large data file from beginning to end is performing sequential reads; an application appending records to a growing file is performing sequential writes. Random I/O instead accesses scattered locations, such as database index pages. A single workload can contain both patterns, so storage selection should reflect actual behavior rather than the application category alone.

The main performance objective for large sequential transfers is usually throughput, measured in MB/s or MiB/s. IOPS measures operations per second, while latency measures how long an operation takes. These metrics are related but not interchangeable. At the same operation rate, larger transfers move more data, until another limit is reached. For example, 1,000 operations per second at 256 KiB per operation represents approximately 250 MiB/s of application data before accounting for overhead and storage-specific request handling.

Sequential access is particularly valuable on hard disk drives because adjacent reads or writes reduce mechanical seeking. SSDs also support sequential workloads, but their advantage over HDDs is often more important for random access and low latency. Sequential access does not require physically adjacent storage devices or sectors: cloud storage abstracts physical placement, and applications generally control logical access order rather than the provider's underlying layout.

For cost-optimized cloud architecture, first determine whether the application needs block, file, or object storage. A batch processor that scans large files on an attached block volume may be a candidate for throughput-oriented HDD storage. In Amazon EBS, Throughput Optimized HDD volumes, called st1, target frequently accessed, large sequential workloads, while Cold HDD volumes, called sc1, target less frequently accessed workloads with lower throughput requirements. Neither volume type supports boot volumes. Compare these choices with SSD options such as gp3 when latency, mixed access, or workload variability matters.

Object storage can be suitable for backups, media, and analytical datasets that applications read in large portions. However, sequential access does not turn object storage into a block device or a general-purpose appendable file system. Request charges, storage class retrieval charges, minimum storage durations, and data transfer costs may affect the economics. For analytics, partitioning data and selecting only required columns can save more than simply increasing sequential scan speed because they reduce the amount of data read.

Applications can improve sequential performance through buffering, appropriately sized requests, read-ahead, and enough concurrent operations to keep the storage path busy. These techniques have trade-offs: buffering consumes memory, read-ahead wastes resources when predictions are wrong, and delayed writes require explicit durability handling. Multiple individually sequential readers can also create a less sequential aggregate pattern when they share a storage device.

Benchmark representative file sizes, request sizes, concurrency, and read/write proportions. Check storage throughput limits, compute-instance storage bandwidth, network capacity, and any burst-credit behavior; a short test can hide a lower sustained rate. In certification questions, large sequential transfers and relaxed latency requirements suggest evaluating throughput-oriented, lower-cost storage, not automatically selecting the highest-IOPS SSD. The correct choice must still meet access frequency, durability, availability, and recovery requirements.

## Learn Sequential I/O in lessons

4 short lessons on Sequential I/O in 2 certification courses.

- SAA-C03: Random I/O and Sequential I/O: distinguishing access patterns (Premium), https://app.blowstack.com/lessons/random-i-o-and-sequential-i-o-distinguishing-access-patterns-saa-c03
- SAP-C03: Random I/O and Sequential I/O: distinguishing access patterns (Premium), https://app.blowstack.com/lessons/random-i-o-and-sequential-i-o-distinguishing-access-patterns-sap-c03
- SAA-C03: Sequential I/O: throughput-oriented storage selection (Premium), https://app.blowstack.com/lessons/sequential-i-o-throughput-oriented-storage-selection-saa-c03
- SAP-C03: Sequential I/O: sizing for sustained throughput (Premium), https://app.blowstack.com/lessons/sequential-i-o-sizing-for-sustained-throughput-sap-c03
