Bufferbloat has become a severe degradation to performance in contemporary IP networks, especially to low-latency Internet traffic that has strong delay and jitter requirements. Over buffering in network equipments which initially is supposed to eliminate the loss of packets and enhance the throughput, tend to create continuously long queues, and consequently cause swelling end-to end latency and subpar Quality-of-Experience (QoE). In this paper, the author examines the effects of bufferbloat on the application performance of cars relying on latency sensitive applications: Voice over IP (VoIP), online gaming, augmented and virtual reality (AR/VR) and real-time teleoperation. We initial discuss the underlying causes of bufferbloat, namely buffer size, conservative drop policy and the interaction between transport layer congestion control and transport layer congestion control. The paper subsequently defines low-latency traffic needs and points out that it is susceptible to queueing and jitter delays, as well as bursty packet loss. A controlled testbed based on access-network conditions with mixed traffic loads is used as an experimental evaluation. The drop-tail buffering is contrasted with Active Queue Management (AQM) methods to measure their impacts in terms of latency, throughput, fairness and coexistence with the legacy TCP flows. Findings show that uncontrolled buffers have a significant negative effect on the performance of low-latency traffic in congestion but that AQM mechanisms can be carefully tuned to achieve a substantial reduction in queueing delay without seriously impacting throughput. Lastly, the paper explains the open issues regarding bufferbloat in wireless networks and mobile networks, new applications based on ultra-low-latency, and the correct measurement and detection of operational networks. The results offer empirical evidence to the network designers and researchers whose goal is to develop latency-sensitive Internet infrastructures.
Dr. Sudhanshu Gonge¹, Dr Kalyani Kadam², Dr. Deepak Yashwant et al.· Journal of Intelligent Decis...· 0 citations
Peer-to-peer (P2P) overlay networks are the basis of numerous large-scale distributed applications since they provide the ability to share resources, distribute content, and offer collaborative services without a central authority. Nonetheless, due to the openness and dynamism nature of P2P systems, they are very susceptible to failures, node churning, network partitions and maliciousness. Creation of robust overlay network is hence critical in ensuring reliability, availability and performance during unfavorable conditions. In this paper, the design principles, threat models and protocol mechanisms necessary to create fault-tolerant and secure P2P overlays are investigated. It initially examines the main properties of structured and unstructured overlay networks with emphasis made to the topology construction of the networks, their maintenance mechanisms, and their routing mechanism. This paper will then examine some of the most critical failure and attack models such as dynamic membership changes, link failures, Byzantine nodes and coordinated attacks, which worsen overlay performance. Based on this discussion, the paper provides resilient protocol architecture design of join, leave, and reconfiguration procedures, and fault-tolerant routing and look-up algorithms, including Chord successor list routing, k-redundant path routing, and self-healing overlay routing. The issue of security conscious resilience mechanisms is also discussed to reduce malicious behavior without compromising scalability. As an analytical discussion and comparative assessment results in, the findings indicate that redundancy, adaptability and self-healing properties can enhance overlay robustness without incurring too much overhead. At the end of the paper, design trade-offs and future directions of resilient P2P overlay networks in new decentralized applications have been highlighted.
Dr. Sudhanshu Gonge¹, Dr Kalyani Kadam², Dr. Deepak Yashwant et al.· Journal of Intelligent Decis...· 0 citations
We use cookies to run the site and, with your consent, for analytics and to show ads.
See our Cookie Policy.
