<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Its actually not all that different than what the libraries would
be running into with a swamped receive utilization from patron traffic.
Even though you're looking to do a primarily transmit operation, the
devices still talk back and forth, so if your receive utilization is
maxed, the response from the server on the other end gets delayed,
which slows the whole operation. <br>
<br>
The main thing we're doing with QoS at our core isn't targeted at
doing things like limiting MySpace traffic to only 50% of the line, its
making sure that when someone does something like requests a page from
your web server, the small request gets through quickly so the server
can send out its large response on the underutilized transmit bandwidth.<br>
<br>
Also, in response to Travis's anecdote, I'd like to remind everyone
that in the coming cold winter months, please try and always have at
least a small amount of traffic on your connections to prevent the
lines from freezing.<br>
<br>
<pre class="moz-signature" cols="72">Thanks,
Karl Jendretzky
Technology Project Manager
Ohio Public Library Information Network
<a class="moz-txt-link-abbreviated" href="mailto:jendreka@oplin.org">jendreka@oplin.org</a>
(614) 728-1515</pre>
<br>
<br>
Bill Hardison wrote:
<blockquote
cite="mid:f26d80a30808280915m17165755r5279d56ecb40c100@mail.gmail.com"
type="cite">
<div dir="ltr">In my previous incarnation we ran into a similar issue
but in reverse.
We had more data coming IN than our T-1 cared for. It was slowing down
important out-bound traffic such as payroll (accounting servers were
located in some remote portion of Borneo I think). We implemented a
band-aid solution at the time. We purchased a router capable of using
2 T-1 lines and "balanced" some of our load over them. Basically we
reserved T-1a for sales and accounting traffic and T-1b for "web"
traffic. We did use a few cable modems for certain applications. The
place a cable modem was a good idea (and proved reliable) was for
incoming traffic. Since most home broadband configurations are heavy
on download "speeds" and minimal in the upload department, cable modems
were ideal for traffic cams and such.<br>
<br>
The ultimate solution came when Buckeye TeleSystems started
offering Metropolitan Ethernet. Then, we hooked up a big ol' 10MB
Ethernet connection. The cable modems are still in place for the most
part, because they seem to be doing the job that they were asked to do.<br>
<br>
2¢<br>
<br>
Bill<br>
<br>
<br>
Bill Hardison<br>
Computer Services Coordinator<br>
Northwest Regional Library System (NORWELD)<br>
419-352-2903</div>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
OPLINTECH mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OPLINTECH@oplin.org">OPLINTECH@oplin.org</a>
<a class="moz-txt-link-freetext" href="http://mail.oplin.org/mailman/listinfo/oplintech">http://mail.oplin.org/mailman/listinfo/oplintech</a>
</pre>
</blockquote>
</body>
</html>