Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
The fastest way to improve I/O performance is to identify the bottleneck before changing hardware. Measure the real workload, distinguish latency from IOPS and throughput, find which process and layer is waiting, then reduce unnecessary I/O, improve locality and batching, tune concurrency, and only afterward provision faster storage. A premium SSD cannot fix a serialized application, an inefficient query, a saturated VM, or a network limit.
Define what “better I/O” means
Set a measurable target first: lower transaction latency, higher IOPS, more sustained throughput, faster database commits, improved p99 response time, or shorter backup duration. These are different goals.
- Latency: time for one request to complete. Track averages and tail percentiles such as p95, p99 and p99.9.
- IOPS: completed operations per second.
- Throughput: bytes transferred per second.
- Queue depth: outstanding requests waiting or in flight.
- I/O size: bytes per operation.
- Concurrency: number of operations submitted at once.
- Read/write mix: the proportion of reads and writes.
- Utilization: how busy a device or path appears; it is not proof of saturation.
- I/O wait: CPU time waiting for I/O, a symptom rather than a diagnosis.
A useful approximation is:
Throughput ≈ IOPS × I/O sizeFor example, 10,000 4-KiB operations are roughly 39 MiB/s, while 1,000 1-MiB operations are roughly 1,000 MiB/s. Protocol overhead, caching and service limits make real results differ. AWS explains how I/O size and volume type affect these measurements in its EBS I/O characteristics.
Classify the workload
Latency-sensitive workloads
OLTP transactions, metadata-heavy services, small random reads and synchronous durable writes need low and predictable latency, adequate IOPS and controlled queueing. Tail latency often matters more than the average.
#1 Best Overall
- THE SSD ALL-STAR: The latest 870 EVO has indisputable performance, reliability and compatibility built upon Samsung's pioneering technology. S.M.A.R.T. Support: Yes
- EXCELLENCE IN PERFORMANCE: Enjoy professional level SSD performance which maximizes the SATA interface limit to 560 530 MB/s sequential speeds,* accelerates write speeds and maintains long term high performance with a larger variable buffer, Designed for gamers and professionals to handle heavy workloads of high-end PCs, workstations and NAS
- INDUSTRY-DEFINING RELIABILITY: Meet the demands of every task — from everyday computing to 8K video processing, with up to 600 TBW** under a 5-year limited warranty***
- MORE COMPATIBLE THAN EVER: The 870 EVO has been compatibility tested**** for major host systems and applications, including chipsets, motherboards, NAS, and video recording devices
- UPGRADE WITH EASE: Using the 870 EVO SSD is as simple as plugging it into the standard 2.5 inch SATA form factor on your desktop PC or laptop; The renewed migration software takes care of the rest
Throughput-sensitive workloads
Backups, media processing, warehouse scans, ETL and large transfers benefit from sequential access, larger requests and enough parallelism to keep storage busy. AWS notes that SSD-backed volumes suit small or random I/O, while HDD-backed volumes perform best with large sequential operations.
Also record whether access is local or remote, whether requests are synchronous, the working-set size, and whether one operation depends on the previous one.
Measure before changing anything
Take a baseline under normal load. Record read/write IOPS, bandwidth, request size, latency percentiles, queue depth, device utilization, per-process activity, CPU and memory pressure, network traffic, cache hit rate and (for databases) wait events. Repeat during the slowdown, not only when the system is idle.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Linux observation
iostat -xz 1
pidstat -d 1
lsblk -o NAME,TYPE,SIZE,FSTYPE,MOUNTPOINTS,ROTA,SCHED
vmstat 1
free -h
sudo lsof +D /path/to/mountIn iostat, inspect r/s, w/s, rMB/s, wMB/s, avgrq-sz, avgqu-sz, await, r_await, w_await and %util. Sustained latency and queue growth under load are more meaningful than one high utilization reading. Microsoft’s Linux performance guidance explains the fields and their limits.
Windows observation
Use perfmon.exe to collect:
PhysicalDisk(*)Disk Reads/sec
PhysicalDisk(*)Disk Writes/sec
PhysicalDisk(*)Disk Bytes/sec
PhysicalDisk(*)Avg. Disk sec/Read
PhysicalDisk(*)Avg. Disk sec/Write
PhysicalDisk(*)Avg. Disk sec/Transfer
PhysicalDisk(*)Current Disk Queue Length
Process(*)IO Read Operations/sec
Process(*)IO Write Operations/secA sample 15-second collector is:
logman.exe create counter PerfLog-15Sec ^
-o "C:perflogsPerfLog-15Sec.blg" ^
-f bincirc -v mmddhhmm -max 800 ^
-c "LogicalDisk(*)*" "PhysicalDisk(*)*" "Memory*" "Process(*)*" ^
-si 00:00:15Adapt the counter set to the incident. Microsoft’s Windows troubleshooting guide gives latency guidance, but thresholds depend on the device, virtualization and service objective.
Rank #2
- SPEED UP COMPUTER: The fanxiang 1TB SSD 2.5 Inch SATA SSD achieves blazing read and write speeds of 520MB/s, facilitating rapid file and data transfers
- UPGRADE YOUR COMPUTER: Compared to HDDs, the 1TB SATA SSD boots up at least 50% faster, enabling instant productivity or gaming sessions
- LONG-LASTING DURABILITY: The 2.5 SATA SSD 1TB incorporates 3D NAND TLC chips, offering a longer lifespan in writes compared to QLC, ensuring a more reliable data storage solution
- EXTENSIVE COMPATIBILITY: The S101 1TB SATA III SSD is compatible with desktops, laptops, all-in-one PCs, supporting various operating systems like Windows, Linux, and Mac OS, meeting the needs of diverse devices
- 3-Year Service: Fanxiang S101 1TB SSD solid state drive provides 3 years after-sales service and lifetime technical support. If you have any questions, please contact us and we will sincerely and professionally solve the problem for you
Controlled benchmarks
Use a disposable volume or test file and reproduce production block size, access pattern, read/write ratio, worker count, queue depth, cache state and duration. Never point a destructive test at a live device.
fio --name=randread
--filename=/path/to/testfile
--size=8G --bs=4k --rw=randread
--ioengine=io_uring --direct=1
--iodepth=32 --numjobs=4
--runtime=60 --time_based --group_reportingfio --name=seqread
--filename=/path/to/testfile
--size=8G --bs=1M --rw=read
--ioengine=io_uring --direct=1
--iodepth=16 --numjobs=2
--runtime=60 --time_based --group_reporting--direct=1 attempts to bypass the page cache, but behavior varies by operating system and filesystem. Queue depth may be ineffective with some engines, and an 8-GiB file can fit in RAM. Test several sizes and depths, use a dataset representing the working set, and compare latency percentiles as well as IOPS. See the fio documentation.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Find the limiting layer
Trace the complete path:
application → runtime → filesystem → OS scheduler → virtual controller
→ VM or instance bandwidth → network/storage protocol → volume → media- High latency, low IOPS and throughput: investigate serialization, metadata, locks, synchronous flushes, network delay and cache configuration.
- IOPS at the limit: reduce small random operations, batch work, improve locality or provision an SSD/IOPS tier.
- Throughput at the limit: use larger sequential requests, more workers and a volume or VM with higher bandwidth.
- High queue and rising latency: the workload may be over-parallelized or a volume, VM, network or burst-credit limit may be exhausted. Reduce concurrency temporarily and observe p95/p99.
- High I/O wait: identify the issuing process and check storage, filesystem, network, swapping and synchronous writes; I/O wait alone does not identify the cause.
- High disk utilization: correlate it with latency, queue depth, throughput and application response time. Parallel SSD and virtual storage can be busy without being the bottleneck.
Optimize in the least expensive order
1. Eliminate unnecessary I/O
Cache frequently reused data, fix queries that scan unnecessary rows, reduce verbose logging, batch small writes, coalesce records, remove redundant serialization, avoid unbounded polling and separate temporary files from critical data. Compression can reduce storage traffic when its CPU cost is acceptable. Relieve memory pressure that causes paging.
Batching, caching and fewer fsync calls can improve speed but may alter freshness or crash durability. Change durability only when the application’s recovery requirements allow it.
2. Improve locality and request shape
Use sequential access and larger aligned requests for scans, backups and media. Use indexes, partitioning and suitable data formats to avoid database scans. Keep random access where the workload requires it—SSDs handle it well; the objective is to match pattern and device, not to force every workload to be sequential.
Rank #3
- [ Fast and Extraordinary ]: KingSpec 2.5 SATAIII SSD adopts 3D NAND flash memory and semiconductor components, which makes it a high-performance and reliable storage device. Max Sequential read speeds are up to 550 MB/s and max sequential write speeds are up to 520 MB/s. which greatly improves the performance and efficiency of your computer. You get the experience of fast transfers and faster file loading
- [ High-Performance ]: KingSpec 2.5 SATA SSD has the characteristics of shockproof and anti-drop, so you don't have to worry even if the computer drops. Quiet and noiseless, low power consumption, high and low-temperature resistance, faster-booting speed, and program loading speed
- [ More Reliable &More Stable ]:The 2.5" SATA SSD supports wear leveling, garbage collection, over-provisioning, native command queuing, TRIM, S.M.A.R.T, etc, and also passed strict quality-test during the production process. That let it have stable and trustworthy performance, It's great for business and entertainment
- [ Wide Compatibility ]: The Internal SATA SSD compatible with windows 10 / 8.1/8 /7 or later, DOS, Linux, Unix. The interface SATA Rev. 3.0 (6Gb/s) is backward compatible with SATA Rev. 2.0. compatible with laptops, desktops, and all-in-one computers
- [ 3-Year Warranty ]: All KingSpec internal SSD is backed with a 3-year limited warranty, and enjoy lifetime technical support. We have strict control standards for our products, each hard drive has been tested countless times to ensure that there is no quality problem before sending it to you, Any questions or suggestions about the product, We will give you the most sincere service
3. Tune concurrency experimentally
Asynchronous work can keep a fast device busy, but excessive workers increase queueing, CPU overhead, lock contention and tail latency. Add concurrency gradually and stop when the latency objective worsens. AWS gives a workload-specific starting point of about one queue entry per 1,000 available SSD IOPS and recommends testing; this is not a universal rule.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problems4. Choose the I/O model deliberately
Buffered I/O is simple and benefits from the OS cache, but can pollute it and may not be durable when a call returns. Direct I/O reduces page-cache interference but introduces alignment and application-cache responsibilities; it is not automatically faster. Asynchronous APIs, thread pools, scatter/gather and io_uring help when independent operations exist. Research shows io_uring gains depend on workload, batching and queue depth, so profile before adopting it.
5. Tune platform settings only for the workload
For large sequential reads, you can test read-ahead:
sudo blockdev --getra /dev/nvme0n1
sudo blockdev --setra 2048 /dev/nvme0n1AWS warns that increased read-ahead can hurt small random I/O. Keep filesystems below full capacity where fragmentation or metadata exhaustion matters, verify alignment and avoid copying generic scheduler or mount-option recipes across operating systems.
Databases: fix access paths first
Inspect query plans, missing indexes, buffer-pool/shared-memory sizing, temporary-file spills, checkpoints, write-ahead-log placement, bloat and maintenance jobs. Separate read replicas, logs, temporary data and commit-critical storage when appropriate. Connection storms can create disk contention. Engine-specific asynchronous-I/O and durability settings must match the database version, filesystem and crash-recovery requirements; never disable fsync as a generic speed tip. A query reading millions of unnecessary rows often remains slow on faster storage.
Recommended Free Tools
Rank #4
- Upgrade your laptop or desktop computer and feel the difference with super-fast OS boot times and application loads
- Exceptional performance offering up to 550MB/s seq. Read and 500MB/s seq. Write speeds
- Superior performance as compared to traditional hard drives (HDD)
- Ultra-low power consumption
- Backwards compatible with SATA II 3GB/sec
Cloud and virtualization checks
For AWS EBS, compare volume IOPS and throughput with instance EBS bandwidth, aggregate limits, queue length, latency and BurstBalance where applicable. Minute averages can hide microbursts; see the EBS characteristics, performance guidance and EBS-optimized instances.
For Azure, inspect disk and VM IOPS/bandwidth, queue depth, latency, caching, bursting credits and SCSI/NVMe presentation. Azure’s performance limits and disk metrics distinguish disk, VM and cache-served activity.
Document warm versus cold cache and direct versus buffered tests. Snapshot-restored volumes can have higher first-read latency while blocks are initialized or fetched. In Hyper-V, the guest, host, virtual controller and physical storage all contribute; unsuitable VHD/VHDX sector configurations can create read-modify-write overhead. Shared volumes, adapters and network interfaces can also be aggregate bottlenecks.
When new storage is justified
Move from HDD to SATA SSD or NVMe for latency-sensitive random work; choose provisioned-IOPS storage for sustained small-I/O demand and throughput-oriented tiers for large sequential transfers. Increase the VM or instance when its bandwidth cap is the limit. Stripe volumes only when aggregate performance is needed and the redundancy, recovery and operational trade-offs are acceptable. Local ephemeral NVMe is fast but unsuitable for data that must survive host loss.
Free tools Windows power users keep installed
One-click scans. No signup required.
Consider cost, durability, replication, snapshots, endurance, power-loss protection, encryption, migration effort and whether the application can generate enough parallel I/O to use the capacity.
Best Value
- MADE FOR THE MAKERS: Create; Explore; Store; The T7 Portable SSD delivers fast speeds and durable features to back up any endeavor; Build your video editing empire, file your photographs or back up your blogs all in an instant
- SHARE IDEAS IN A FLASH: Don’t waste a second waiting and spend more time doing; The T7 is embedded with PCIe NVMe technology that brings fast read and write speeds up to 1,050/1,000 MB/s¹, making it almost twice as fast as the T5
- ALWAYS MAKE THE SAVE: Compact design with massive capacity; With capacities up to 4TB, save exactly what you need to your drive – from large working files to game data and everything in between
- ADAPTS TO EVERY NEED: Whether using a PC or mobile phone, count on the T7 for extensive compatibility²; It’s a true team player when it comes to heavy-duty application usage or file-saving
- HI RESOLUTION VIDEO RECORDING: Record Ultra High Resolution (4K 60fs) videos directly onto the T7 Portable SSD with your favorite camera or mobile devices; Supports iPhone 15 Pro Res 4K at 60fps video and more³
Validate safely
- Write down the baseline, workload, cache state and success criteria.
- Change one variable at a time and keep a rollback plan.
- Re-test with the same dataset, duration, block size, worker count and load.
- Compare average and p95/p99 latency, IOPS, throughput, CPU, queue depth and application response time.
- Run long enough to expose throttling, burst-credit depletion and sustained-write behavior.
- Keep monitoring after deployment; a benchmark win is not production proof.
Operational checklist
- What exact target is failing: latency, p99, IOPS, throughput or wait time?
- Which process and operation generate the I/O?
- What are block size, access pattern, read/write mix and concurrency?
- Is the dataset cached, and is the test representative?
- Is the limit in the application, memory, filesystem, VM, network or volume?
- Can you reduce, batch or localize the I/O before buying capacity?
- Did the change preserve required durability and recovery behavior?
- Did the same workload improve after re-measurement?
Frequently Asked Questions
Is an SSD always faster?
SSDs generally deliver lower latency and better random I/O than HDDs, but a serialized application, VM cap or inefficient query can remain slow.
What is a good queue depth?
There is no universal value. Use the lowest depth that meets the throughput target without pushing p95/p99 latency beyond the service objective.
Should I enable direct I/O?
Only after testing the specific application and filesystem. It can avoid cache pollution but adds alignment and buffering responsibilities and is not automatically faster.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →How do I benchmark without destroying data?
Use a disposable volume or a test file, verify the path, and never run a raw-device write test on production storage.
Should I increase IOPS or throughput?
Increase IOPS for small random operations and throughput for large sequential transfers—after confirming the volume, VM and network limits are the actual bottleneck.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
