自适应带宽分配?
在我们的文件传输应用程序中,网络性能还不错,
但我们希望获得最大的网络性能,因此一种通过
自适应带宽分配来实现的方法。因此应用程序将被迫获得
可用带宽。朋友们!如果您有任何白皮书或代码可供参考,
那将会非常有帮助:)
谢谢
krishna
In our File Transfer application the network performance was fair
but we want to get the maximum network performance so one way of achieving through
adaptive bandwidth allocation .So the application will be forced to attain the
available bandwidth.friends!!! if u have any white papers or code for reference
it would be much helpful :)
thanks
krishna
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
如果你只是将它扔到 TCP 会话中而不加任何控制,它就会全速传输。
您还可以在传输时压缩文件。它不会加速传输,但会在 CPU 空闲时优化网络的使用。
如果这还不够,唯一进一步改进的[软件]方法是使用多个 TCP 会话,这样您就可以减少 TCP 流量控制上的延迟对速度的限制影响。我相信从同一文件的不同偏移量进行 5 个并发传输就可以完成这项工作,更快是不可能的。
If you just throw it at the TCP session with no control, it will transfer at full speed.
You could also compact the file as you transfer. It will not accelerate the transfer, but will optmize the use of the network, at CPU coast.
If it is not enough, the only [software] way to improve that even more is by using multiple TCP sessions so you will reduce the speed delimitating effects of the latency over the TCP flow control. I beleave 5 concurrent transfers from different offsets of the same file will do the job, faster impossible.
我不认为“自适应带宽分配”真的意味着任何有形的东西(考虑到它是该表达的谷歌排名第二!),但我会尝试给出一个答案,可能会帮助您提出更好的问题。
如果应用程序的网络活动可以并行化(bittorrent 就是一个很好的例子),那么这是实现更快网络传输的一种方法。
但总的来说,对于用户空间应用程序来说,出于充分的原因,网络条件将超出应用程序的控制范围。如果用户空间应用程序认为调整或影响外部操作系统级网络条件是其任务的一部分,我会认为它是恶意软件。例如,QoS 可用于确定与您的应用程序相关的流量的优先级,但您可能会这样做想要在部署指南中建议和解释,而不是尝试从应用程序内部进行管理。
I don't think "adaptive bandwidth allocation" really means anything tangible (considering it's the #2 google hit for that expression!) but I'll try to give an answer that might help you ask a better question.
If an application's network activity can be parallelised (bittorrent is a good example of this) then this is one way of achieving faster network transfers.
In general though, for user space applications the networking conditions are going to be outside the application's control for good reasons. If a userspace application considers it part of its mandate to adjust or affect external operating system-level networking conditions I would consider it malware. QoS for example could be used to prioritise the traffic associated with your application but that is something you might want to suggest and explain in a deployment guide and not try to manage from within your application.