On Mon, 2009-12-07 at 18:50 -0600, Wilson, Eric wrote:
> Theresa;
> 
> When you say the speedtest.net produces good results, what exactly
> does that mean?  What speeds do they report for each scenario?

speedtest.net

download 3.67 Mb/s
upload 0.48Mb/s
ping 22 ms


cablemo.net

download 3.11 8Mbps
upload 0.48 Mbps

In both cases, that's better than our paid cable plan calls for.

> Browser speed results are somewhat objective and depend on how the
> images are rendered.  What speeds are determined from non-brower based
> tasks (e.g. scp, ftp, sftp, or BitTorrent copies) 

Haven't tried other tasks.  With the browser test, from an opened
Firefox browser pointing to the home page, I started the wireshark
capture, put "http://www.theregister.co.uk"; into the URL bar and hit the
"enter" key.  I figured the test as being "done" when the resulting
page, including all its embedded ads and links, was completely done
loading.

> What speeds are observed on the local network amongst the various
> clients?

Not noticing any delay in accessing the NAS device or the networked
printer.

> What are the DNS settings for each client?  Are DNS timeouts a
> possibility?

Nothing peculiar in /etc/dhcp3/dhclient.conf and nothing
in /etc/resolv.conf except the nameserver IP addresses provided by our
ISP (as in, I did not create those entries, they were generated by
NetworkManager automatically).  Ethernet connection was configured to
connect automatically by Automatic (DHCP) Method.

When I was running the old router and OpenBSD firewall, I had the
Ethernet connection set to manual (IP address, subnet, gateway,
nameserver, dns) and disabled IPV6 settings by adding this line
to /etc/sysctl.conf:

"net.ipv4.tcp_window_scaling=0"

You can disable it temporarily by running this from a command line as
root, too:

"echo 0 > /proc/sys/net/ipv4/tcp_window_scaling"

That line has been commented out of /etc/sysctl.conf; I tried turning
the IPV4 scaling back on temporarily, and that does not do anything to
improve things.

If DNS timeouts are a possibility, then why is it that Firefox in the
host computer (Ubuntu 9.04) is bog-slow; Firefox in any Linux virtual
box (Ubuntu 9.04, 9.10, CentOS 5.4) is bog-slow; Firefox in a Windows
virtual box (W2K) is fast as a screaming meemie?

Thanks for the support, though ... this is frustrating!

Theresa

> Cheers;
> 
> E!
> 
> 
> 
> On Mon, Dec 7, 2009 at 4:05 PM, Theresa Kehoe <[email protected]> wrote:
>         Installed a new 8-port Cisco Linksys router last week.
>          Noticed by
>         Friday that web performance was very sluggish.  Any URL takes
>         5-15
>         seconds to load.  Same behavior on both home computers.  Both
>         run Ubuntu
>         (one 8.10, the other 9.04), both use Firefox for web
>         browsing.  Figured
>         I'd wait until Monday, see if it got worked out, if not, would
>         call.
>         
>         Note, speed tests say my connection speed is great (both Cable
>         America's
>         test, and www.speedtest.net)
>         
>         Called Monday; on advice of tech, disconnected router.
>          Plugged cable
>         modem directly into one desktop computer (running Ubuntu
>         8.04).  Reset
>         modem, then rebooted computer.  Same problem.  So, reconnected
>         router.
>         
>         Then I started doing some testing to see if changing browser
>         or
>         operating system makes a difference.  System used for test:
>         
>         Host computer, Intel Core 2 Duo E7400 @ 2.80 GHz, 4GB RAM,
>         Intel 82566DC
>         Gigabit Network Connection, running fully updated Ubuntu 9.04
>         i386,
>         kernel 2.6.28-17-generic.  Web browser is Firefox 3.0.15.
>          Host runs Sun
>         VirtualBox 3.0.12.  VirtualBox clients include CentOS 5.4,
>         Ubuntu 9.04
>         and 9.10, and Windows 2000.
>         
>         Test:  Launch Firefox, browse to http://www.theregister.co.uk
>         and time
>         how long it takes for the page to fully load.  Capture eth0
>         traffic with
>         Wireshark; save logs.
>         
>         Results:
>         
>         1. Using Firefox 3.0.15 on host, takes 19 seconds to load.
>         
>         2. Using CentOS 5.4 as client, Firefox 3.0.12 as browser,
>         takes 45
>         seconds to load.
>         
>         3. Using Windows 2000 as client, Firefox 3.0 as browser, takes
>         4 seconds
>         to load.
>         
>         Note, did not log Wireshark, but using Firefox 3.5, using
>         Opera, or
>         running Ubuntu in a VirtualBox is just as slow.  Other web
>         sites, same
>         behavior.  Once a connection to a site is established, further
>         navigation within that site runs reasonably well.
>         
>         In the Windows 2000 virtual client, using either IE or
>         Firefox, all web
>         sites load quickly.
>         
>         I am certainly perplexed! -- does anyone have any ideas, or is
>         anyone
>         willing to plow through the Wireshark log files?
>         
>         Theresa
>         
>         --
>         Central West End Linux Users Group (via Google Groups)
>         Main page: http://www.cwelug.org
>         To post: [email protected]
>         To subscribe: [email protected]
>         To unsubscribe: [email protected]
>         More options: http://groups.google.com/group/cwelug
> 
> 
> 
> -- 
> Central West End Linux Users Group (via Google Groups)
> Main page: http://www.cwelug.org
> To post: [email protected]
> To subscribe: [email protected]
> To unsubscribe: [email protected]
> More options: http://groups.google.com/group/cwelug

-- 
Central West End Linux Users Group (via Google Groups)
Main page: http://www.cwelug.org
To post: [email protected]
To subscribe: [email protected]
To unsubscribe: [email protected]
More options: http://groups.google.com/group/cwelug

Reply via email to