Recording With Fraps
| Overall Statistics | Fraps Recording |
|---|---|
| Elapsed Time | 27:30 |
| Read Operations | 8954 |
| Write Operations | 223 582 |
| Data Read | 573.76 MB |
| Data Written | 23.65 GB |
| Disk Busy Time | 80.96 s |
| Average Data Rate | 306.20 MB/s |
Although console gamers need capture cards to record their best moves, PC enthusiasts have the luxury of using Fraps instead. Of course, recording adds a very intensive task on top of gaming, particularly if the title is a demanding first-person shooter, for example. Not only do you have the game's overhead, but then there's the uncompressed video file being written in the background.
Let's put this into perspective. Playing through Battlefield 3's Kaffarov mission involves reading ~500 MB (mostly at a queue depth of one) with very few writes. If you're also recording gameplay with Fraps, the storage profile changes significantly. Suddenly, the majority of accesses are sequential writes queued more than two operations deep. The amount of data that we have to store is staggering too. After 27 minutes of game play, we end up with close to 24 GB of raw, uncompressed video.
I/O Trends:
- 25% of all operations occur at a queue depth of one
- 59% of all operations occur at queue depths between two and four
- 10% of all operations occur at a queue depth of five
- 97% of all data transferred is sequential
- 84% of all operations are 128 KB in transfer size
