From: "Martin A. Fink" <fink@mpe.mpg.de>
To: Alan <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: SATA-performance: Linux vs. FreeBSD
Date: Tue, 13 Feb 2007 13:32:34 +0100 [thread overview]
Message-ID: <200702131332.34899.fink@mpe.mpg.de> (raw)
In-Reply-To: <20070213112527.59eaa504@localhost.localdomain>
Am Dienstag, 13. Februar 2007 12:25 schrieben Sie:
> > Well they do. The Flash disk I have (SATA-I) is capable of 48 MB/s and
this
> > value is reached over the whole disk size by windows as well as by
FreeBSD.
> > See my test results in the first thread.
>
> Ok a flash disk should be more stable
>
> > My Seagate Barracuda Harddisk drive (SATA-II) starts with 76 MB/s and
> > decreases linearly to 35 MB/s due to the fact that it has to write to a
> > rotating disk. But on a flash disk there is nothing rotating...
>
> The hard disk one isn't guaranteed or stable but the flash especially if
> it is aimed at it ought to behave.
>
> > So where is the difference between SATA-I and SATA-II ?
>
> All physical side if they are on the same controller when you do the
> tests. Mostly latency,
>
> > And why is FreeBSD able to write with constant rates (the complete 25 GB,
all
> > with 48+/-0.1 MB/s) but Linux 2.6.18 not ?
>
> Does the FreeBSD fsync sync to media ? Also what controller is being used
> here, and do you have EHCI USB support running ?
Manual of FreeBSD fsync says it syncs to media.
I used the same controller: Same computer, same harddisk. two partitions on
the system disk, one for linux, one for freebsd.
EHCI:
ehci_hcd 0000:00:1d.7: EHCI Host Controller
ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: Product: EHCI Host Controller
AHCI
ahci 0000:00:1f.2: AHCI 0001.0100 32 slots 4 ports 3 Gbps 0xf impl SATA mode
>
> > With a dedicated (rotating) SATA II device, using the first 70% of disk
space
> > no problem -- tested ! With a SATA-I device only a problem with Linux
2.6.18
>
> I suspect the SATA-1 itself may not be the decider but something else -
> eg the hard disk using NCQ, which would cover up any latency related
> problems.
>
> > Journaling of data: you are right, ext2 performs better than ext3.
>
> And ext3 in writeback mode ought in theory (but practice is always
> harder ;)) be faster than ext2.
>
>
--
Dipl. Physiker
Martin Anton Fink
Max Planck Institute for extraterrestrial Physics
Giessenbachstrasse
85741 Garching
Germany
Tel. +49-(0)89-30000-3645
Fax. +49-(0)89-30000-3569
next prev parent reply other threads:[~2007-02-13 12:32 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-12 14:02 Martin A. Fink
2007-02-12 17:04 ` Andi Kleen
2007-02-12 16:27 ` Martin A. Fink
2007-02-12 18:41 ` Andi Kleen
2007-02-12 17:56 ` Martin A. Fink
2007-02-12 18:17 ` Ray Lee
2007-02-12 19:08 ` Alan
2007-02-12 20:34 ` Nigel Cunningham
2007-02-13 9:34 ` Martin A. Fink
2007-02-13 11:25 ` Alan
2007-02-13 12:32 ` Martin A. Fink [this message]
2007-02-13 14:47 ` Theodore Tso
2007-02-13 15:03 ` Alan
2007-02-13 17:12 ` Jeff Garzik
2007-02-12 23:31 ` Matthias Schniedermeyer
2007-02-13 9:25 ` Martin A. Fink
2007-02-13 10:08 ` Arjan van de Ven
2007-02-13 11:18 ` Andi Kleen
2007-02-13 10:25 ` Arjan van de Ven
2007-02-13 11:27 ` Alan
2007-02-13 11:59 ` Jörn Engel
2007-02-13 19:54 ` Jeffrey Hundstad
2007-02-13 10:16 ` Matthias Schniedermeyer
2007-02-13 10:29 ` Martin A. Fink
2007-02-13 12:04 ` Jörn Engel
2007-02-13 12:24 ` Matthias Schniedermeyer
2007-02-13 12:49 ` Martin A. Fink
2007-02-13 13:53 ` Matthias Schniedermeyer
2007-02-12 16:37 ` Martin A. Fink
2007-02-12 18:19 ` Stefan Richter
2007-02-13 19:09 ` Jeff Carr
2007-02-12 17:42 ` Martin A. Fink
2007-02-15 5:48 ` Tejun Heo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200702131332.34899.fink@mpe.mpg.de \
--to=fink@mpe.mpg.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®