From: PFC <lists@peufeu.com>
To: reiserfs-list@namesys.com
Subject: Re: reiserfs performance on ssd
Date: Fri, 28 Apr 2006 09:07:21 +0200 [thread overview]
Message-ID: <op.s8ph2jz5cigqcu@apollo13> (raw)
In-Reply-To: <e692861c0604271025t8b60d9cn9aa47d68de55df5a@mail.gmail.com>
While I like the idea, the iram implementation is horrible for various
reasons :
- no ECC
- It uses SATA hence only a very little part of the RAM speed is used,
and large latencies are introduced.
- I wouldn't trust it for critical data.
Then, it would be faster to just add the RAM on the motherboard and
create a ramdisk...
Also : THE PCI BUS MUST DIE !
It's no wonder reiserfs is slower on this thing ; reiserfs is optimized
for hard disks which have high seek latencies.
For RAM storage, things like hash tables are a lot better than trees,
because you don't care about sequential scanning and locality of
reference... (as long as the items are a bit larger than a cache line,
which is obviously the case here).
A filesystem that pauses and thinks for 0.5 ms of CPU time to avoid a 5
ms HDD seek time is a good thing, but for SSD storage you want a FS that
doesn't think at all.
Using ReiserFS on this is like hitting a nail with a screwdriver.
Try tmpfs, I'm curious about the results.
Crazy idea :
- Ask the motherboard manufacturer to stick a battery on the mobo so that
the contents of RAM survive reboot
- Tweak the BIOS so that RAM isn't cleared at boot
- Teach the Kernel to be cautious while booting and not overwrite the
previous RAMDISK
- You have persistent ramdisk. Stick your reiserfs journal on it, enjoy.
next prev parent reply other threads:[~2006-04-28 7:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-27 13:16 reiserfs performance on ssd Jure Pečar
2006-04-27 13:47 ` Sander
2006-04-27 14:28 ` Gregory Maxwell
2006-04-27 16:20 ` Toby Thain
2006-04-27 16:20 ` Toby Thain
2006-04-27 17:25 ` Gregory Maxwell
2006-04-28 7:07 ` PFC [this message]
2006-04-28 8:20 ` Andreas Dilger
2006-04-28 12:37 ` Jure Pečar
2006-04-28 17:37 ` Perry Kundert
[not found] ` <1146145299.5436.52.camel@localhost.localdomain>
2006-04-27 13:48 ` Sander
2006-04-27 13:58 ` Ming Zhang
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=op.s8ph2jz5cigqcu@apollo13 \
--to=lists@peufeu.com \
--cc=reiserfs-list@namesys.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.