2 ms·
That wastes tape capacity when the drive inevitably has to stop and restart. It's cheaper to run the tape slower (you can adjust it so that it is very close to
by zaarn 7y ago
That wastes tape capacity when the drive inevitably has to stop and restart.
It's cheaper to run the tape slower (you can adjust it so that it is very close to what you can sustainably deliver)
- Dylan16807 7y ago> That wastes tape capacity when the drive inevitably has to stop and restart. Not meaningfully, unless there's something ridiculous about the format I'm unaware of. A full tape write covers 160-200 linear kilometers. Stopping 10 times, which is once per hour, is barely anything. I haven't found anything listing the exact size of gaps, but I did find a post from someone having thousands of buffer underruns that was only losing half a second of capacity per underrun.
- adrian_b 7y agoAs Dylan16807 also said, you waste very little. I am using 6 TB LTO-7 tapes and I group the data written to the tapes in files of approximately 50 GB, which are read from a NVMe SSD. This means that each 50 GB file is written at 3 Gb/s, the maximum tape speed, but after each 50 GB the tape is stopped then restarted. So I write on each tape about 120 files with an aggregate size of up to 45 905 860 blocks of 131 072 bytes each. That is more than the 6.0 TB advertised for the tapes, so I do not waste any measurable tape capacity. The 50 GB file size is chosen because it fits inside the 64 GB RAM of the computer with the tape drive and certain algorithms that I am using to process the tape files (lrzip & par2, for compression & redundancy) are faster when the entire file fits in the RAM.