pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: KuroiNeko <evpopkov@carrier.kiev.ua>
To: pgsql-sql@postgresql.org
Subject: Re: benchmarks
Date: Sat, 28 Oct 2000 21:00:05 +0000
Message-ID: <39FB3E55.nailLJ1IK8VB@ed.ed> (raw)
References: <200010271836.e9RIaNZ96055@hub.org>
	<39FA7133.AEEE0D40@agliodbs.com>

>  Comparing PostgreSQL to MySQL is  like comparing an 18-wheel Kenworth to
> a Porsche. The two are not equivalent

 That's it. Major differences in features makes any benchmarking `apples to
oranges.'

> ... if you want a simple, very
> very fast READ-ONLY database, use MySQL.

 BTW, can it  be used on a  r/o partition, or it still  writes something to
the files (locks, stats)?

>  If you want a full-featured transaction-environment database for a huge,
> complex set of data, use PostgreSQL.

 Even if the  system is relatively small and simple....  Everything will go
down in fires, this is the law. So,  the first thing to think about is what
will  your options  be when  you're trying  to keep  the parts.  Stress and
torture tests would be more usefull than benchmarking.

>  Any benchmarks  you find are  likely comapring  the two for  hosting web
> sites, which is unfair to PostgreSQL.

 IIRC,  there was  one  in favor  PGSQL  (wasn't it  run  by the  Bridge?).
However, the very  fact of benchmarking these two  along with non-disclosed
commercial products, where  PGSQL wins with flying colours,  IMHO does more
harm than good.

> If everything your database needs
> to do is serve up page content, go for MySQL.

 How 'bout flat files? They will be even faster. Main advantage of DBMS, as
I  see  it, is  a  possibility  to  build searchable,  logically  connected
structures, with consistency and concurrency  supported on the server side.
With MySQL  one has neither  referential integrity, nor server  side logic.
Moreof, HTML pages are bad as  textual attributes even when tuple/page size
limitation can be easily worked around.
 If you  want dynamic  content, SSI  and CGI will  do, and  there's nothing
about DBMS. Storing page templates as BLOBs gives nothing but slowdown.

>  If  you've  got   to  build  a  60-user   inventory  management  system,
> MySQL  won't  even  bring you  close  -  heck,  it's  not even  close  to
> SQL92-compliant.

 It's still  possible, one  can even  get it for  $ 200,  but TCO  will sky
rocket when it starts to phreak, or when business rules will be changed.


--

 contaminated fish and microchips
  huge supertankers on Arabian trips
 oily propaganda from the leaders' lips
  all about the future
 there's people over here, people over there
  everybody's looking for a little more air
 crossing all the borders just to take their share
  planning for the future

 Rainbow, Difficult to Cure



view thread (6+ messages)  latest in thread

Message-ID: <39FB3E55.nailLJ1IK8VB@ed.ed>
Permalink:  ../39FB3E55.nailLJ1IK8VB@ed.ed/
Also on:    postgresql.org/message-id/39FB3E55.nailLJ1IK8VB@ed.ed

 · 

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-sql@postgresql.org
  Cc: evpopkov@carrier.kiev.ua
  Subject: Re: benchmarks
  In-Reply-To: <39FB3E55.nailLJ1IK8VB@ed.ed>
  References: <200010271836.e9RIaNZ96055@hub.org> <39FA7133.AEEE0D40@agliodbs.com> <39FB3E55.nailLJ1IK8VB@ed.ed>

* 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