It does list the IOPS, but I don't have the block-size. (although I will
admit the engrish is a bit hard to read ;p)

IOPS 20,000 per SATA port (you can split RAM into two ports, it appears as
two devices, apparently)

Personally I'm quite a bit more comfortable with dumping to a CF then
trying to keep refreshing the memory with battery. Seems to be that It
would be far less prone to issues, especially considering that the CF would
only be being written when the power has been off for greater then 30 sec.
(this is not on the web site, but in the manual, which is in the support
section, although they emailed my a copy)

Andrew Hettinger
http://Prominic.NET  ||  [EMAIL PROTECTED]
Tel:  866.339.3169 (toll free) -or- +1.217.356.2888 x.110 (int'l)
Fax: 866.372.3356 (toll free) -or- +1.217.356.3356            (int'l)
Mobile direct: 1.217.621.2540
CompTIA A+, CompTIA Network+, MCP

"Andrey Kuzmin" <[EMAIL PROTECTED]> wrote on 10/21/2008 02:44:24
PM:

> [image removed]
>
> Re: [storage-discuss] Recommended slog/ZIL size?
>
> Andrey Kuzmin
>
> to:
>
> Andrew M. Hettinger
>
> 10/21/2008 02:54 PM
>
> Cc:
>
> storage-discuss
>
> Looks good, although 200 MBps data transfer rate doesn't tell much w/o
> block size, IOPS would have been more useful.
>
> Further, dumping memory contents to CF card on power failure doesn't
> seem a production-level solution, though I'm probably exaggerating a
> non-issue here :).
>
> Regards,
> Andrey
>
>
>
> On Tue, Oct 21, 2008 at 10:26 PM, Andrew M. Hettinger
> <[EMAIL PROTECTED]> wrote:
> > I am going to be attempting to do the same thing with an ACard
ANS-9010B.
> >
> > http://www.acard.com.tw/english/fb01-product.jsp?
> idno_no=271&prod_no=ANS-9010B&type1_title=%20Solid%20State%
> 20Drive&type1_idno=13
> >
> > They report "Out Of Stock," and their sales rep I talked to today said
he
> > just shipped me the last two in the US. He said they should have more
> > available next month. I will try and report on my results. (If this
works
> > well, this company needs a larger web presence. it took me about a day
of
> > searching to find this.)
> >
> > note: they support ECC, they appear to actually use SATA 300 (rather
then
> > the iRAM's SATA150 interface). Also the battery is used only to dump
the
> > memory to a compact flash on a failure, not to keep refreshing the
dram.
> >
> > Andrew Hettinger
> > http://Prominic.NET || [EMAIL PROTECTED]
> > Tel: 866.339.3169 (toll free) -or- +1.217.356.2888 x.110 (int'l)
> > Fax: 866.372.3356 (toll free) -or- +1.217.356.3356 (int'l)
> > Mobile direct: 1.217.621.2540
> > CompTIA A+, CompTIA Network+, MCP
> >
> > Eric Sproul ---10/20/2008 03:39:49 PM---Andrey Kuzmin wrote: > As to
X25-E
> > (released today), this indeed would be a worthwhile try as
> >
> >
> > From:
> > Eric Sproul <[EMAIL PROTECTED]>
> > To:
> > [email protected]
> > Date:
> > 10/20/2008 03:39 PM
> > Subject:
> > Re: [storage-discuss] Recommended slog/ZIL size?
> > Sent by:
> > [EMAIL PROTECTED]
> > ________________________________
> >
> >
> > Andrey Kuzmin wrote:
> >> As to X25-E (released today), this indeed would be a worthwhile try as
> >> both ZIL and L2ARC device (I believe the latter, if not both, has
> >> already been explored at Sun).
> >
> > Update to my saga:  I'm thoroughly disappointed with Mtron 3035 drives,
but
> > maybe they are just not suited for server use at all.  The random write
> > performance is worse than a mechanical drive!
> >
> > At this point, we're looking to put ZIL on an NVRAM-based device, the
> > Gigabyte
> > I-RAM with 4GB of memory (its max.)
> > http://www.gigabyte.com.tw/Products/Storage/
> Products_Overview.aspx?ProductID=2180
> >
> > In advance of getting that, I did a rough approximation of its
performance
> > by
> > creating a 4GB file in /tmp and lofi-mounting it.  I turned off swap to
> > ensure
> > the file didn't ever get swapped out of main memory (I have 32GB in
this
> > box, so
> > it's not an issue, and it's a test system anyway.)
> >
> > # zpool destroy data
> > # swap -d /dev/zvol/dsk/rpool/swap
> > # mkfile 4g /tmp/slogfile
> > # lofiadm -a /tmp/slogfile
> > # zpool create data raidz \
> >    c0t2d0 c0t3d0 c0t4d0 c0t5d0 c0t6d0 c0t7d0 log /dev/lofi/1
> >
> > Of course, I can't reboot or crash without losing my ZIL, but thisis a
test
> > box, and I'd never run it this way in production.  Nevertheless,
performance
> > is
> > impressive, as we expect:
> >                    extended device statistics
> >    r/s    w/s   kr/s   kw/s wait actv wsvc_t asvc_t  %w  %b device
> >    0.0 6148.2    0.0 786974.6 26.6  3.4    4.3    0.6  86  86 lofi1
> >
> >>6000 write IOPS, or roughly 200x more than we were getting with the
Mtrons.
> >
> > We'll also be evaluating the Intel X-25E as soon as we can get our
grubby
> > little
> > hands on one.  :)
> >
> > Eric
> > _______________________________________________
> > storage-discuss mailing list
> > [email protected]
> > http://mail.opensolaris.org/mailman/listinfo/storage-discuss
> >
> >
> >
> > _______________________________________________
> > storage-discuss mailing list
> > [email protected]
> > http://mail.opensolaris.org/mailman/listinfo/storage-discuss
> >
> >
_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss

Reply via email to