Suppose you have to implement video streaming platform from scratch.
(假设您必须从头开始实现视频流平台。)
It doesn't matter where you gonna store metadata, your not-very-popular video files will be stored at file system, or object store in case you want to use Cloud.(不管您将元数据存储在哪里，都可以将不太受欢迎的视频文件存储在文件系统或对象存储中，以防您想使用Cloud。)
If you'll choose AWS, in order to boost AWS S3 read performance, you can make multiple read requests against the same video file, see Performance Guidelines for Amazon S3 :(如果您选择AWS，则为了提高AWS S3的读取性能，您可以针对同一视频文件发出多个读取请求，请参阅Amazon S3的性能指南 ：)
You can use concurrent connections to Amazon S3 to fetch different byte ranges from within the same object.
(您可以使用到Amazon S3的并发连接从同一对象中获取不同的字节范围。)
This helps you achieve higher aggregate throughput versus a single whole-object request.(与单个完整对象请求相比，这可以帮助您实现更高的总吞吐量。)
In the same time, as you know, disk I/O is sequential for all HDD/SDD drives, so to boost read performance (if neglect RAM necessary for uncompress/decrypt each video chunk) you have to read from multiple disks (YouTube use RAID).
(如您所知，同时，所有HDD / SDD驱动器的磁盘I / O都是顺序的，因此要提高读取性能（如果忽略RAM来解压缩/解密每个视频块所必需），则必须从多个磁盘读取（YouTube使用）袭击）。)
Why S3 will have better performance on concurrent byte range requests agains the same file?
(为什么S3在并发字节范围请求和同一个文件上会有更好的性能？)
Isn't it stored on single disk?(它不存储在单个磁盘上吗？)
I suppose S3 may have some replication factor and still store the file on multiple disks, does it?(我想S3可能有一些复制因素，但仍将文件存储在多个磁盘上，对吗？)
ask by VB_ translate from so
