On Fri, 21 Jan 2000, Paul D. Robertson wrote:

> I'd doubt though that all 3-400 of his users will be sitting on the same
> Ethernet segment (if they are, the speed of the gateway won't much matter,
> there will be worse problems.)  The latency issues of 300 people all
> hitting that gateway at once will be noticable (and measurable.)  Enough
> so that if the internal topology isn't laid out well, it's worth putting
> in and outbound interfaces on the box just to drive down collisions on
> the internal interface.  Unfortunately, in current stable Linux kernels,
> that means an immediate degragation in performance.

can you go into more detail on this statement? the aratecture that I
assumed for this is 100Mb full duplex ethernet to a switch which then has
the internal users on it, on the outside i only have 2 T-1 lines so even
10Mb ethernet should be reasonable.

> "It works." is significantly different from "It works well." which is
> still different from "This is as good as it gets."  I'd expect a liberal
> arts college to put heavier use on streaming protocols and that's where
> latency can bite the most.

Agreed, in my case it falls into the "it works well" catagory, we just
switched out the linux box for a Sun ultra 10 333MHz 256M ram running
Raptor, performance has not changed notisably.

> The first night everyone's stuck inside because of (pick your favorite
> natural weather phenoninom) it'd suck to see a meltdown.
> 
> With business users, you can figure on a high of about 15% active
> concurrent sockets for your users.  20% is about the highest I've seen it
> yet.  In a college dorm in Iowa during a snowstorm I'd expect it to be
> higher.

Depends on the company :-) So far we have decided that until bandwidth
starts to cost us more then it is now we do not object to realaudio
streams, combining this with the fact that the building is in a
radio black hole so people cannot bring in radios, there are a surprising
number of people attaching to realaudio "stations" all day long wearing
headphones while they work.


-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]

Reply via email to