From owner-freebsd-scsi Tue Apr 7 12:39:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA23652 for freebsd-scsi-outgoing; Tue, 7 Apr 1998 12:39:47 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from heathers2.stdio.com (kyle@heathers2.stdio.com [199.89.192.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA23634 for ; Tue, 7 Apr 1998 12:39:45 -0700 (PDT) (envelope-from kyle@stdio.com) Received: (from kyle@localhost) by heathers2.stdio.com (8.8.8/8.8.8) id PAA04936; Tue, 7 Apr 1998 15:37:24 -0400 (EDT) Date: Tue, 7 Apr 1998 15:37:23 -0400 (EDT) From: Kyle McPeek To: freebsd-scsi@FreeBSD.ORG Subject: CAM Performance... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi All, For a project at work I need to be able to write 400MB sequentially to an Ultra-Wide harddisk (Seagate ST32171W 2GB) from an nfs mounted drive as fast a possible. right now we have it down to around 3:45 seconds using the old scsi code. I am using dd with bs=27163 (Approximately = data on one track) to write to /dev/rsd0s2c. Would the cam code improve sequential scsi writes? Also, what sort of general speed improvements has everyone seen using the cam code? I do still plan to test the cam code myself, but I would like to know what other people have experienced. Kyle McPeek TEKsystems Consultant at Lexmark International. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message