From: "Martin A. Fink" <fink@mpe.mpg.de>
To: Matthias Schniedermeyer <ms@citd.de>, linux-kernel@vger.kernel.org
Subject: Re: SATA-performance: Linux vs. FreeBSD
Date: Tue, 13 Feb 2007 13:49:05 +0100 [thread overview]
Message-ID: <200702131349.05428.fink@mpe.mpg.de> (raw)
In-Reply-To: <45D1AE13.9000504@citd.de>
Am Dienstag, 13. Februar 2007 13:24 schrieben Sie:
> Martin A. Fink wrote:
>
> >> Also you have skipped the information how the images "arrive" on the
system
> > (PCI(e) card?), that may be important for an "end to end" view of the
> > problem.
> >
> > Images arrive via Gigabit Ethernet. GigE Vision standard. (PCIe x4)
>
> The the next question is: ChipSet/Used Protocol/JumboFrames/(NAPI)/... .
>
> Have you already determined the load caused by this part?
> Depending on the GigE-Chipset, and Protocol/JumboFrames/(NAPI)/..., the
involved overhead can be quite serious.
>
> >> And what's also missing. What is "a long period of time".
> >> Calculating best-case with the SSD:
> >> 27GB divided by 30MB/s only gives a bit more than 15 Minutes.
> >> And worst case with 50MB/s is less than 10 Minutes.
> >
> > Well. The testdrive has 27GB. The final drive will have 225 GB. And there
will
> > be 3 cameras and thus 3 disks. This means we talk about 140 MB/s for
around
> > 90 minutes.
> > For space applications with low power but high performance this is a long
> > time... ;-)
>
> The MB/CPU/RAM will be the one specified in the first mail?
> My gut feeling says: Forget it.
>
> The needed total bandwidth may be to high and at least the incoming part via
GigE may have serious overhead.
> 150MB/s in via (at least 2) GigE, without Zero-Copy there is another 150MB/s
memory to memory.
> Then there is the next 150MB/s memory to the discs, without Zero-Copy there
also another 150MB/s memory to memory.
> In total that's 300MB/s to 600MB/s without any processing.
I dont understand your calculation: from 3 GE ports come around 50 MB/each.
These altogether 150MB/s have to be copied to memory. From there they will be
copied to disk. So we talk about 2x150 MB/s running through my system. That
is less than 2 PCIe lanes can handle... And there are more than 2 lanes
between north and south bridge....
>
> But on the other hand, hdparm -T says my system (Core2Duo E6700, FSB1066,
2GB DDR2-800 RAM, 32Bit) has a buffer-cache bandwidth around 4000MB/s.
> As you don't said which FSB and Memory-Type you have i would guess that your
system should reach between 2000MB/s and 3500MB/s of LINEAR(!) memory
bandwidth.
> (Total usable Memory-Bandwidth is unfortunately also dependent on usage
pattern. Large & linear is not as important as with a rotating HDD, but it
factors in)
>
>
>
> Btw. On the topic of filesystem and Linux performance:
> SGI did a "really big" test some time ago width a big iron having 24
Itanium2-CPUs in 12 nodes, and 12*2 GB of ram and having 256 discs using
XFS(Which is from SGI!).
> The pdf-file is here:
> http://oss.sgi.com/projects/xfs/papers/ols2006/ols-2006-paper.pdf
>
> According the the paper the system had a theoretical peak IO-performance of
11.5 GB/s and practically peaked at 10.7GB/s reading and 8.9GB/s writing.
> IOW Linux and XFS CAN perform quite well, but the system has to have enough
muscle for the job.
> And since the paper (and Kernel 2.6.5) the development of Linux hasn't
stopped.
>
>
>
> --
> Real Programmers consider "what you see is what you get" to be just as
> bad a concept in Text Editors as it is in women. No, the Real Programmer
> wants a "you asked for it, you got it" text editor -- complicated,
> cryptic, powerful, unforgiving, dangerous.
>
>
--
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:49 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-12 14:02 SATA-performance: Linux vs. FreeBSD 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
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 [this message]
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=200702131349.05428.fink@mpe.mpg.de \
--to=fink@mpe.mpg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ms@citd.de \
/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