pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Hannu Krosing <hannu@tm.ee>
To: Christopher Browne <cbbrowne@libertyrms.info>
Cc: pgsql-performance@postgresql.org
Subject: Re: inferior SCSI performance
Date: Thu, 02 Oct 2003 10:13:53 +0300
Message-ID: <1065078832.3166.77.camel@fuji.krosing.net> (raw)
In-Reply-To: <60brt1szby.fsf@dev6.int.libertyrms.info>
References: <20031001103338.GA29293@libertyrms.info>
	<Pine.LNX.4.33.0310010713250.20754-100000@css120.ihs.com>
	<20031001132536.GA30269@libertyrms.info>
	<60brt1szby.fsf@dev6.int.libertyrms.info>

Christopher Browne kirjutas K, 01.10.2003 kell 19:21:

> 
> The FS-related result appeared surprising, as the "stories" I had
> heard suggested that JFS hadn't been particularly heavily tuned on
> Linux, whereas XFS was supposed to be the "speed demon."

Gentoo linux recommends XFS only for SAN+fibre channel + good ups for
anything but database use ;)

> It is entirely possible that the result I saw was one that would
> reverse partially or even totally on a system LACKING that cache.  XFS
> might "play better" when we're cacheless; the (perhaps only fabled)
> demerits of JFS being more than totally hidden if we add the cache.
> 
> What I find disappointing is that it isn't possible to get SSD cards
> that are relatively inexpensive.  A similarly fabulous performance
> increase _ought_ to be attainable if you could stick pg_xlog and
> pg_clog on a 256MB (or bigger!) battery-backed SSD, ideally one that
> plugs into a PCI slot.

For really cheap and for small-size transactions you could experiment
with USB2 memory sticks (some of them claim 34MB/s write speed), perhaps
in striped/mirrored configuration. You would just need something
counting writes in the driver layer to alert you when you are reaching
the x00k "writes" limit and have to plug in new sticks :)

OTOH, articles I found through quick googling suggest only 2.4MB/s write
and 7MB/s read speeds for USB 2.0 memory sticks, so the 34MB is proably
just sales pitch and refers to bus speed, not actual write speed ;(

> Unfortunately, while there are companies hawking SSDs, they are in the
> "you'll have to talk to our salescritter for pricing" category, which
> means that they must be ferociously expensive.  :-(.

the cheapest I found was the one with external backup power was ~1.8k$
for 2GB PCI device

http://www.cdw.com/shop/search/Results.aspx?key=platypus&x=0&y=0

An external 16GB one with battery backup and
write-t-small-ide-drives-on-power-failure was ~25k$

-----------------
Hannu



view thread (11+ messages)  latest in thread

Message-ID: <1065078832.3166.77.camel@fuji.krosing.net>
Permalink:  ../1065078832.3166.77.camel@fuji.krosing.net/
Also on:    postgresql.org/message-id/1065078832.3166.77.camel@fuji.krosing.net

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: hannu@tm.ee, cbbrowne@libertyrms.info
  Subject: Re: inferior SCSI performance
  In-Reply-To: <1065078832.3166.77.camel@fuji.krosing.net>
  References: <20031001103338.GA29293@libertyrms.info> <Pine.LNX.4.33.0310010713250.20754-100000@css120.ihs.com> <20031001132536.GA30269@libertyrms.info> <60brt1szby.fsf@dev6.int.libertyrms.info> <1065078832.3166.77.camel@fuji.krosing.net>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox