From owner-freebsd-questions@FreeBSD.ORG Thu Jan 4 17:56:00 2007 Return-Path: X-Original-To: questions@freebsd.org Delivered-To: freebsd-questions@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 37F4B16A415 for ; Thu, 4 Jan 2007 17:56:00 +0000 (UTC) (envelope-from bobmc@bobmc.net) Received: from smtp-out.fcibroadband.com (smtp-out.fcibroadband.com [64.119.104.17]) by mx1.freebsd.org (Postfix) with ESMTP id F3BF713C44C for ; Thu, 4 Jan 2007 17:55:59 +0000 (UTC) (envelope-from bobmc@bobmc.net) Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp-in1.fcibroadband.com (Postfix) with ESMTP id 7A49F1B2374 for ; Thu, 4 Jan 2007 12:55:59 -0500 (EST) Received: from smtp-out1 ([127.0.0.1]) by localhost (smtp-out1 [127.0.0.1]) (amavisd-new, port 10025) with SMTP id 17804-03 for ; Thu, 4 Jan 2007 12:55:56 -0500 (EST) Received: from [192.168.1.102] (unknown [209.104.171.81]) by smtp-out.fcibroadband.com (Postfix) with ESMTP id B51AD1B2368 for ; Thu, 4 Jan 2007 12:55:56 -0500 (EST) Message-ID: <459D3F37.80002@bobmc.net> Date: Thu, 04 Jan 2007 12:53:59 -0500 From: Bob McIsaac User-Agent: Thunderbird 1.5 (X11/20060317) To: questions@freebsd.org Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: network tuning and performance troubleshooting X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Jan 2007 17:56:00 -0000 Josh Carroll wrote: Problem: Browser status 'looking up address' for 10 seconds for any web page clicked. Slashdot takes almost a minute to load. But FTP performance is good and running a shoutcast stream is no problem. Sending mail via my ISP is slow. How about a large transfer over http with fetch or wget? Does it perform as well as an ftp connection? It could be a DNS problem. Try a dig of slashdot.org and see what the query time is: dig A slashdot.org | grep 'Query time' Run that a few times and see how fast it's resolving. It should be on the order of a 100ms or less, at least after the first query. Josh $ dig A slashdot.org | grep 'Query time' ;; Query time: 95 msec $ dig A slashdot.org | grep 'Query time' ;; Query time: 15 msec $ dig A slashdot.org | grep 'Query time' ;; Query time: 7 msec $ dig A slashdot.org | grep 'Query time' ;; Query time: 11 msec $ fetch -v [1]http://www.freebsd.org/ports/growth/status.png looking up [2]www.freebsd.org connecting to [3]www.freebsd.org:80 requesting [4]http://www.freebsd.org/ports/growth/status.png local size / mtime: 4725 / 1163039436 remote size / mtime: 4725 / 1163039436 status.png 100% of 4725 B 53 kBps $ fetch -v [5]http://www.kde.org/screenshots/images/3.5/01-welcome.png looking up [6]www.kde.org connecting to [7]www.kde.org:80 requesting [8]http://www.kde.org/screenshots/images/3.5/01-welcome.png remote size / mtime: 185546 / 1145367871 01-welcome.png 100% of 181 kB 177 kBps $ The numbers above seem sensible for 'dig' but fetch is not reporting the looking/connecting time which is seconds more than the download time. On google.maps the screen is divided into a grid and it takes a few seconds to fill in each one. I always thought it was a single image. References 1. http://www.freebsd.org/ports/growth/status.png 2. http://www.freebsd.org/ 3. http://www.freebsd.org/ 4. http://www.freebsd.org/ports/growth/status.png 5. http://www.kde.org/screenshots/images/3.5/01-welcome.png 6. http://www.kde.org/ 7. http://www.kde.org/ 8. http://www.kde.org/screenshots/images/3.5/01-welcome.png