Re: Question: BlockSize > 8192 with FusionIO

Test,

Sorry trying to fix why my email is getting formatted to bits when posting to the list.

- John

-----Original Message-----
From: pgsql-performance-owner@postgresql.org [mailto:pgsql-performance-owner@postgresql.org] On Behalf Of Strange, John
W
Sent: Tuesday, January 04, 2011 1:01 PM
To: Ben Chobot; Merlin Moncure
Cc: pgsql-performance@postgresql.org Performance
Subject: Re: [PERFORM] Question: BlockSize > 8192 with FusionIO

This has gotten a lot better with the 2.x drivers as well.



I'm completely aware of the FusionIO and it's advantages/disadvantages.. I'm currently getting the following pgbench
resultsbut still only hitting the array for about 800MB/sec, short of the 3GB/sec that it's capable of.  This is simply
atrash DB for us to store results in for short periods of time.  If something bad was to happen we can regenerate the
results. So performance with limited risk is what we are looking to achieve. 
 



asgprod@ASH01_riskresults $ pgbench -v -j 4 -t 200000 -c 16 -h localhost -p 4410 pgbench_10000

starting vacuum...end.

starting vacuum pgbench_accounts...end.

transaction type: TPC-B (sort of)

scaling factor: 10000

query mode: simple

number of clients: 16

number of threads: 4

number of transactions per client: 200000

number of transactions actually processed: 3200000/3200000

tps = 16783.841042 (including connections establishing)

tps = 16785.592722 (excluding connections establishing)





-----Original Message-----

From: pgsql-performance-owner@postgresql.org [mailto:pgsql-performance-owner@postgresql.org] On Behalf Of Ben Chobot

Sent: Tuesday, January 04, 2011 12:37 PM

To: Merlin Moncure

Cc: pgsql-performance@postgresql.org Performance

Subject: Re: [PERFORM] Question: BlockSize > 8192 with FusionIO





On Jan 4, 2011, at 8:48 AM, Merlin Moncure wrote:



> 

> most flash drives, especially mlc flash, use huge blocks anyways on

> physical level.  the numbers claimed here

> (http://www.fusionio.com/products/iodrive/)  (141k write iops) are

> simply not believable without write buffering.  i didn't see any note

> of how fault tolerance is maintained through the buffer (anyone

> know?).



FusionIO buffers. They have capacitors onboard to protect against crashing and power failure. They passed our crash
attemptsto corrupt writes to them before we put them into production, for whatever that's worth, but they do take a
longtime to come back online after an unclean shutdown.
 

-- 

Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)

To make changes to your subscription:

http://www.postgresql.org/mailpref/pgsql-performance

This communication is for informational purposes only. It is not
intended as an offer or solicitation for the purchase or sale of
any financial instrument or as an official confirmation of any
transaction. All market prices, data and other information are not
warranted as to completeness or accuracy and are subject to change
without notice. Any comments or statements made herein do not
necessarily reflect those of JPMorgan Chase & Co., its subsidiaries
and affiliates.



This transmission may contain information that is privileged,
confidential, legally privileged, and/or exempt from disclosure
under applicable law. If you are not the intended recipient, you
are hereby notified that any disclosure, copying, distribution, or
use of the information contained herein (including any reliance
thereon) is STRICTLY PROHIBITED. Although this transmission and any
attachments are believed to be free of any virus or other defect
that might affect any computer system into which it is received and
opened, it is the responsibility of the recipient to ensure that it
is virus free and no responsibility is accepted by JPMorgan Chase &
Co., its subsidiaries and affiliates, as applicable, for any loss
or damage arising in any way from its use. If you received this
transmission in error, please immediately contact the sender and
destroy the material in its entirety, whether in electronic or hard
copy format. Thank you.



Please refer to http://www.jpmorgan.com/pages/disclosures for
disclosures relating to European legal entities.

-- 
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
This communication is for informational purposes only. It is not
intended as an offer or solicitation for the purchase or sale of
any financial instrument or as an official confirmation of any
transaction. All market prices, data and other information are not
warranted as to completeness or accuracy and are subject to change
without notice. Any comments or statements made herein do not
necessarily reflect those of JPMorgan Chase & Co., its subsidiaries
and affiliates.

This transmission may contain information that is privileged,
confidential, legally privileged, and/or exempt from disclosure
under applicable law. If you are not the intended recipient, you
are hereby notified that any disclosure, copying, distribution, or
use of the information contained herein (including any reliance
thereon) is STRICTLY PROHIBITED. Although this transmission and any
attachments are believed to be free of any virus or other defect
that might affect any computer system into which it is received and
opened, it is the responsibility of the recipient to ensure that it
is virus free and no responsibility is accepted by JPMorgan Chase &
Co., its subsidiaries and affiliates, as applicable, for any loss
or damage arising in any way from its use. If you received this
transmission in error, please immediately contact the sender and
destroy the material in its entirety, whether in electronic or hard
copy format. Thank you.

Please refer to http://www.jpmorgan.com/pages/disclosures for
disclosures relating to European legal entities.