Modelling of retrieval latency for proxy cache simulation

2001 ◽  
Vol 37 (3) ◽  
pp. 167 ◽  
Author(s):  
J. Kim ◽  
H. Bahn ◽  
K. Koh ◽  
Y. Baek
2013 ◽  
Vol 2013 ◽  
pp. 1-16 ◽  
Author(s):  
Chenghao Liu ◽  
Miska M. Hannuksela ◽  
Moncef Gabbouj

Due to the fact that proxy-driven proxy cache management and the client-driven streaming solution of Dynamic Adaptive Streaming over HTTP (DASH) are two independent processes, some difficulties and challenges arise in media data management at the proxy cache and rate adaptation at the DASH client. This paper presents a novel client-driven joint proxy cache management and DASH rate adaptation method, named CLICRA, which moves prefetching intelligence from the proxy cache to the client. Based on the philosophy of CLICRA, this paper proposes a rate adaptation algorithm, which selects bitrates for the next media segments to be requested by using the predicted buffered media time in the client. CLICRA is realized by conveying information on the segments that are likely to be fetched subsequently to the proxy cache so that it can use the information for prefetching. Simulation results show that the proposed method outperforms the conventional segment-fetch-time-based rate adaptation and the proxy-driven proxy cache management significantly not only in streaming quality at the client but also in bandwidth and storage usage in proxy caches.


2004 ◽  
Vol 14 (1) ◽  
pp. 34-47 ◽  
Author(s):  
Hsiang‐Fu Yu ◽  
Yi‐Ming Chen ◽  
Li‐Ming Tseng

2020 ◽  
Vol 245 ◽  
pp. 07026
Author(s):  
Dave Dykstra

The WLCG Web Proxy Auto Discovery (WPAD) service provides a convenient mechanism for jobs running anywhere on the WLCG to dynamically discover web proxy cache servers that are nearby. The web proxy caches are general purpose for a number of different http applications, but different applications have different usage characteristics and not all proxy caches are engineered to work with the heaviest loads. For this reason, the initial sources of information for WLCG WPAD were the static configurations that ATLAS and CMS maintain for the Conditions data that they read through the Frontier Distributed Database system, which is the most demanding popular WLCG application for web proxy caches. That works well for use at traditional statically defined WLCG sites, but now that usage of commercial clouds is increasing, there is also a need for web proxy caches to dynamically register themselves as they are created. A package called Shoal had already been created to manage dynamically created web proxy caches. This paper describes the integration of the Shoal package into the WLCG WPAD system, such that both statically and dynamically created web proxy caches can be located from a single source. It also describes other improvements to the WLCG WPAD system since the last CHEP publication.


2021 ◽  
Vol 3 (3.2) ◽  
pp. 95-111
Author(s):  
Marco Vinicio Ramos Valencia ◽  
Steven Alejandro Salazar Cazco ◽  
Jhonatan Guillermo Díaz León ◽  
José Alberto Rivadeneira Romero
Keyword(s):  

Introducción, el consumo de ancho de banda es un recurso valioso en las empresas hoy en día, la necesidad de mejorar constantemente los tiempos de respuesta en las solicitudes de los servicios web ha provocado que se busquen medios eficientes que cumplan con los requerimientos de la red, disminuyendo el ancho de banda que se consume. Objetivo, analizar la reducción del consumo de ancho de banda de un ISP mediante el estudio de Servidor Web Proxy Cache para la empresa FASTNET CIA. LTDA. Metodología, el diseño de la investigación fue cuantitativa. Se realizó un análisis de la red TELCO aplicando la Metodología Integral para Redes Avanzadas (MIRA) obteniendo así sus fortalezas y debilidades. Consecuentemente se estudiaron diferentes opciones de servidores web proxy caché, entre ellos: HAARPCACHE, RAPTOR CACHE, SQUID, THUNDERCACHE, ampliando el abanico de opciones para una implementación adecuada. se configuraron tres escenarios; el primero basa su estructura en el nodo “Nat Langos AS” sin ninguna variante, el segundo escenario se diferenció por tener incorporado el servidor HAARPCACHE instalado sobre el servidor HP Proliant dl-385P y el tercero cambia el servidor por RAPTOR CACHE implementado en el mismo ordenador. Resultados, el servidor HAARPCACHE cumplió en un 90% de dichas condiciones y provocó un 17,86% de ahorro de ancho de banda empresarial, mientras que RAPTORCACHE cumplió con el 45% de las medidas y creó un ahorro correspondiente al 8,92%. Conclusiones, se concluye que el servidor más adecuado para FASTNET CIA. LTDA. por su fiabilidad y capacidad de ahorro es HAARPCACHE, además de una considerable reducción del ancho de banda mejorando así el performance de los usuarios.


Sign in / Sign up

Export Citation Format

Share Document