Jay, Does this mean you have determined your network is the bottleneck of your http traffic? If you think the congestion in your network is slowing down the response time, then doing the QoS stuff surely will help, of course, as long as the traffic stays within your network, but why adding bandwidth to solve the congestion problem is not a choice? I think it is better than playing with QoS. If you want to go down this road, you may also want to make sure the users could verify that your network is not slowing down their http traffic, if you only prioritize http, the users may use ping to verify the response. you could add icmp to high priority too, but why not just giving icmp a high priority, this way they will always see your network is responding pretty quick :-).
I think there are some networks are selling QoS as a service, but IMHO if you just want to improve the response time, it may not be worth the trouble. Just my .02 Kent ----- Original Message ----- From: "Jay Greenberg" To: Sent: Friday, July 26, 2002 9:49 AM Subject: ISP QoS Architecture Question [7:49767] > I am considering deploying QoS features in our ISP. The ISP has about > 60 thousand users in total, and I was thinking of setting a general > traffic policy. E.g., I would like to set HTTP traffic down to a very > low delay, to make the network seem faster to end users. I suppose > what I am asking is - has anyone done this for an ISP, and if so, how > did it turn out? > > > Jay Greenberg Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=50045&t=49767 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
