From: bathurst@noaapmel.gov (Bill Bathurst)
Subject: Re: _Long_ response to lag questions - Hit 'n' now
Organization: NOAA/PMEL, Sand Point Way, Seattle, WA
	<JIVE.92Nov13101842@spanky.ssc.gov>
Date: Fri, 13 Nov 1992 18:55:44 GMT

In article <JIVE.92Nov13101842@spanky.ssc.gov> jive@spanky.ssc.gov (Jim Ivey) writes:

	However, about this lag thing:)  I finally decided to compile ping
   times yesterday, after the umpteenth post mentioning Fill's lag.  Each is
   done with a 1000 byte packet, and a 1000 count. i.e. ping -s
   bronco.ece.cmu.edu 1000 1000  


I think 1000 byte packets are way too large.  I am not exactly sure what
a good example packet size would be for netrek... how about 128 byte packets?

                           I just complain a lot, as most people have noted:)
   I'm sure those boys from Lagg U and 3000ms have worse.  But at least they
   have a local server:)

We have different sources of lagg.  We play on xterminals and machines that
are heavily used.  Most UW players are home machine lagged/niced.  Here are 
some sample times from some of our *fast* machines (Sparc II's):

doorstop.design.iastate.edu:
  yang> /usr/etc/ping -sv doorstop.design.iastate.edu 128 20

  20 packets transmitted, 20 packets received, 0% packet loss
  round-trip (ms)  min/avg/max = 60/1005/6650

  yang> /usr/etc/ping -sv doorstop.design.iastate.edu 1000 20
  
  20 packets transmitted, 19 packets received, 5% packet loss
  round-trip (ms)  min/avg/max = 93/100/120

rwd4.mach.cs.cmu.edu:
  stormy> /usr/etc/ping -sv rwd4.mach.cs.cmu.edu 128 20

  20 packets transmitted, 18 packets received, 10% packet loss
  round-trip (ms)  min/avg/max = 74/81/123

  stormy> /usr/etc/ping -sv rwd4.mach.cs.cmu.edu 1000 20

  20 packets transmitted, 20 packets received, 0% packet loss
  round-trip (ms)  min/avg/max = 97/106/143

calvin.usc.edu:
  stormy> /usr/etc/ping -sv calvin.usc.edu 1000 20

  20 packets transmitted, 19 packets received, 5% packet loss
  round-trip (ms)  min/avg/max = 81/156/1321

  stormy> /usr/etc/ping -sv calvin.usc.edu 128 20

  20 packets transmitted, 20 packets received, 0% packet loss
  round-trip (ms)  min/avg/max = 39/51/91

bronco.ece.cmu.edu:
  /usr/etc/ping -sv bronco.ece.cmu.edu 128 20

  20 packets transmitted, 0 packets received, 100% packet loss <- down?
  
I notice lagg for us can be good late at night.  We seem to compete with
a lot of ethernet traffic so our response is *burpy*.  A good example is
playing at Calvin where I get frequent burps, especially when there is
a lot of torps flying on the screen.

A lot of players play from machines where they have CPU quotas.  They
get niced quite quickly on those machines.  I am impressed they can
actually play decently when I watch over there shoulders.  It like
the screen will update once per second when they try an ogg.  Wheeeee!!!!

As for bronco the lagg was better when they had it at 5 updates.  I think
the home folks set their updates up to 9.  I can't blame them because it
is much *easier* to phaser lock cloakers at 9 updates/sec since the galatic
map updates much more frequently!





--
Bill Bathurst				Internet:	bathurst@noaapmel.gov 
NOAA/PMEL				Phone:		(206) 526-6205

Newsgroups: rec.games.netrek