通过 HTTPS 发送大文件时的性能影响
可能的重复：
HTTP 与 HTTPS 性能
通过 HTTPS 发送较大文件（例如 10-15 MB）时（而不是HTTP）对性能有何影响（如果有）？ （这些文件是 CSV）谢谢。
Possible Duplicate:
HTTP vs HTTPS performance
When sending larger files (e.g. 10-15 MB) over HTTPS (as opposed to HTTP) what are the performance implications (if any)? (the files are CSVs) Thanks.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
HTTPS 比 HTTP 更需要 CPU 资源。要确定这在您的使用场景中是否可行，一个好方法是进行测试和测量。
一般来说，我认为这两种工具都不是适合这项工作的工具。一个潜在的问题是并非所有服务器都支持恢复中断的传输。此外，HTTPS 通常不进行任何压缩。
您可以在这个重复问题中找到一个很好的答案。
HTTPS is more CPU intensive than HTTP. A good way to find out if that is OK or not in your usage scenario is to test and measure.
Generally speaking, I'd say that neither is the right tool for the job. One potential problem is that not all server support resume of interrupted transfers. Also, HTTPS normally doesn't do any compression.
You'll find a good answer in this duplicate question.
查看这个答案...
HTTP 与 HTTPS 性能
...然后测量性能。测试这一点并查看您的特定设置中的性能特征应该非常简单。
Check out this answer...
HTTP vs HTTPS performance
... and then measure the performance. It should be very simple to test this and see what the performance characteristics are in your particular setup.
显然 HTTP 与 HTTPS 性能 有很多细节，但请记住 SSL 的大量成本位于会话设置中，因此对于大型传输来说，传输加密的成本（相对）较低。
Obviously HTTP vs HTTPS performance has lots of details, but remember that a lot of the cost of SSL is in the session setup, so the encryption for the transfer will be less costly (relatively) for a large transfer.