On Saturday 15 March 2008 16:22, Willy Tarreau wrote:
For example?
Anecdote time. Remember there used to be "brand name" floppy disks and
generic floppy disks, and the brand name ones cost a lot more because
they were supposedly safer? Well, big secret, studies were done and
the no-name disks came out better. Why? Because selling at commodity
prices the generic makers could not afford returns. So they made them
well.
It is like that with PCs. Supposedly you get a lot more reliability
when you spend more money and buy all high end near-custom gear. In
fact, the cheap stuff just keeps on chugging, because those guys can't
afford to have it break.
So please don't underestimate the reliability of a PC.
There are bits of Linux that are undeniably dodgy. We get a lot of bug
reports about usb for example, keyboards just quitting and it's not the
keyboard's fault. Just say no to usb in a server, at least until some
fundamental cleanup happens there.
The worst bug I've seen in a server this year? A buggy bios in a Dell
server that would issue a keyboard error and sit and wait for somebody
to press F1 when there was no keyboard attached. That is embedded
software for you. Personally, I think we do way better than that in
Linux.
Yes. Dual power supplies are highly recommended for this application.
With dual power supplies you can carry out preemptive maintenance on
the UPS.
So mirror two of them, I keep saying. If that is not good enough for
you, then make it three way, and replicate for good measure. The thing
is, none of that hurts the microsecond level performance, and it gets
you whatever data security you desire. Whereas anything that requires
waiting on disk transactions does hurt performance. Since my interest
currently lies in high performance, that is where my effort goes. And
do I need to say it: patches gratefully accepted.
For my immediate application... hacking the kernel in comfort... just
replicating will provide all the data safety I need.
Right. What we are talking about is filling in a missing level in the
cache hierarchy, something like:
L1 .3 ns
L2 3 ns
L3 30 ns
Ramdisk 2 us
Flash 20 us
Disk 3 ms
Approximate, numbers not necessarily too accurate, but you know what I
mean. Currently there is this gigantic performance cliff between L3
memory and disk. Something like the Violin ramdisk fills it in nicely.
And see, you still need that rotating media because it always will be
an order of magnitude cheaper than flash. Tape might still fit in
there too, though these days it seems increasingly doubtful.
Daniel
--
