You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Jack Bates (JIRA)" <ji...@apache.org> on 2014/08/29 01:17:10 UTC
[jira] [Commented] (TS-2597) QoS (Quality of Service) Support ZPH
(Zero Penalty HIT)
[ https://issues.apache.org/jira/browse/TS-2597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14114572#comment-14114572 ]
Jack Bates commented on TS-2597:
--------------------------------
I added some notes on this and traffic shaping in general to the wiki:
https://cwiki.apache.org/confluence/display/TS/Traffic+Shaping#TrafficShaping-ZeroPenaltyHit
I'm skeptical that it isn't better to directly manage the bandwidth between the proxy and origin? I think the use case for this Squid feature is the management of upstream bandwidth without limiting access to content that's already cached. You can mark traffic sent *from* the origin with the CONNMARK iptables/ip6tables target. That and transparency can help directly manage the bandwidth between the proxy and origin.
> QoS (Quality of Service) Support ZPH (Zero Penalty HIT)
> -------------------------------------------------------
>
> Key: TS-2597
> URL: https://issues.apache.org/jira/browse/TS-2597
> Project: Traffic Server
> Issue Type: New Feature
> Components: Plugins
> Reporter: Faysal Banna
> Fix For: sometime
>
>
> Hello there.
> I know it would be easy for someone in development team to create a module (plugin) that enables to set QoS markers on outgoing traffic.
> as such :
> Allows admin to set a TOS/Diffserv value to mark local hits.
> thus allowing missed (non locally cached )objects to have certain TOS/Diffserv and HITs (locally cached) objects to have different TOS/Diffserv.
> Much Regards
> Faysal Banna
--
This message was sent by Atlassian JIRA
(v6.2#6252)