谷歌云存储 - 静态内容（使用多个带有负载均衡器的存储桶对性能的影响）（初学者问题）
我有一些静态内容，将被大量并发用户下载。我正在使用谷歌云存储桶来提供这些内容。
我担心由于带宽或文件读取速度而导致性能低下。如果并发用户数量较多。 我想问一下，如果使用多个带有负载均衡器的存储桶来提供相同的内容是否会更好，或者不会有太大差异？
I have some static contents which will be downloaded by a big number of concurrent users. I am using a google cloud storage bucket to serve those contents.
i am afraid of low performance due to bandwidth, or file read speed. in case of big number of concurrent users.
i want to ask if is it better to use more than one bucket with a load balancer to serve the same contents, or there will not be much difference?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我没有使用多个存储桶进行基准测试，但我认为不会有任何好处。缺点是您部署的复杂性增加。
云存储已经非常快，可以处理全局访问。我不认为单个负载平衡器能够超载储物桶。有例外，例如对象名称 hotspots ），但这也会影响您的多个水桶策略。
您还可以配置双区域存储桶，这些储物桶主要用于复制数据。选择一个水桶位置将具有更多影响 link 。
客户端快速性能的关键是两个方面。网络性能和局部性。
对于网络性能，请确保数据通过Google的高级层网络从存储桶传播到用户。这降低了互联网的不可预测性。
要改善本地性，请将数据更接近客户端。这意味着使用Google的 cdn ，它在“ noreflow noreferrer”> points-of-prosence 更接近客户端。
读取速度将由客户端的网络速度（Internet连接）和TCP/IP堆栈配置确定。云存储的数量级更快。
为了获得最佳性能：
云存储的最佳实践
I have not benchmarked using multiple buckets, but I do not think there will be any benefit. The downside is increased complexity in your deployments.
Cloud Storage is already very fast and can handle global access. I do not believe a single load balancer would be able to overload a storage bucket. There are exceptions such as object name hotspots (sequential object names), but this would also affect your multiple bucket strategy.
You can also configure dual-region storage buckets, which are primarily used for replicating data. Selecting a bucket location will have more of an impact link.
The key to fast performance for the client is two-fold. Network performance and locality.
For network performance, ensure data travels from the bucket to the user over Google's premium tier network. This reduces the unpredictability of the Internet.
To improve locality, bring the data closer to the client. This means using Google's CDN, which caches bucket data around the world at points-of-presence that are closer to the client.
Read speed will be determined by the client's network speed (Internet connection) and TCP/IP stack configuration. Cloud Storage is many orders of magnitude faster.
For best performance:
Best practices for Cloud Storage