rec.autos.simulators

NR2003 Server requirements

Schoone

NR2003 Server requirements

by Schoone » Sun, 30 Mar 2003 12:38:19

I agree but on a heavily loaded cable node you will feel the impact more
than if it were on other areas.


> This widely advertised 'failing' of Cable has never been an issue on our
> system.

> The DSL companies used to use this 'shared bandwidth of cable' as a
selling
> point of DSL, but it faded out after a while when it was determined that
it
> wasn't that big of a deal.

> EVERYONE shares somewhere.  Whether it's at the Gateway, backbone,
segment,
> etc...  There's no escaping it, no matter what kind of connection you
have.

> Larry



> > The problem with cable is your impacted more by local users on your
node.
> > If a few people start some big downloads you will see a
> > performance/bandwidth hit.  This is less likely with DSL but it seems
most
> > DSL caps the upload levels lower than cable typically.
> > You may want to look at renting a server if your trying to get some
> regular
> > racing events going, much more consistent and stable way to go IMHO.



> > > Did some speed tests linked from dslreports

> > > Download not an issue getting nearly 2MB
> > > Upload looks like its capped at 475K (maxed at 472K on 5 out of 8
> > > test).

> > > With an average of 22K per car, barely skimp buy hosting 20 cars.
> > > Realistically I think its about 15.  Oh well, there is a local ADSL
> > > offering 2.5 GB down and 640K up but they have a cap on
> > > download/upload per month.  Hopefully my cable company will offer a
> > > "enhanced" cable connection soon.


rec.autos.simulators is a usenet newsgroup formed in December, 1993. As this group was always unmoderated there may be some spam or off topic articles included. Some links do point back to racesimcentral.net as we could not validate the original address. Please report any pages that you believe warrant deletion from this archive (include the link in your email). RaceSimCentral.net is in no way responsible and does not endorse any of the content herein.