|Overall Statistics||Transcoding, CPU|
|Read Operations||144 375|
|Data Read||15.98 GB|
|Data Written||410.58 MB|
|Disk Busy Time||39.72 s|
|Average Data Rate||422.40 MB/s|
This is a repeat of the previous page, except that we're turning off the hardware acceleration and relying on software encoding (CPU only). Interestingly, we end up with a smaller file size. Whereas Quick Sync encoded four files totaling 713 MB, the CPU route results in 373 MB.
We've been touting Quick Sync for the past year. It's clearly a feature that we enjoy. However, we also can't ignore that a vast many enthusiasts aren't running Sandy Bridge-based systems. Even if you do, you might not necessarily want to rely on MediaEspresso or another Quick Sync-enabled transcoding title. HandBrake, for example, remains a popular choice.
However, this trace establishes that, even when you rely on a software encoder, the storage characteristics of the workload don't change. That is to say manipulating multiple files at the same time queues I/O operations deeper.
- 16% of all operations occur at a queue depth of one
- 47% of all operations occur at queue depths between two and four
- 33% of all operations occur at queue depths between five and eight
- 84% of all data transferred is sequential
- 89% of all operations occur are 128 KB in transfer size
- Storage's Role In Content Creation, Explored
- Test Setup And Benchmarks
- Capture Card Recording
- Recording With Fraps
- Transcoding Multiple Streams (Intel Quick Sync)
- Transcoding Multimedia Video (CPU)
- Watching Video Clips
- Editing In Adobe Premiere Pro
- Exporting In Adobe Premiere Pro
- Content Creation Means Lots Of Sequential Data