pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Roberto Mello <rmello@cc.usu.edu>
To: Mathijs Brands <mathijs@ilse.nl>
Cc: Frank Joerdens <frank@joerdens.de>
Cc: pgsql-php@postgresql.org
Subject: Re: persistent connections, AOLserver (Was: [SQL] maybe Offtopic : PostgreSQL & PHP ?)
Date: Fri, 20 Apr 2001 10:36:45 -0600
Message-ID: <20010420103645.B20153@cc.usu.edu> (raw)
In-Reply-To: <20010418202814.B16143@ilse.nl>
References: <B5CDCF382265D311BF33009027A8FE9401E6F3BC@pmrmsg.edsn.com>
	<5.0.2.1.0.20010418223233.00a68170@mail.e-magine.com.au>
	<20010418073430.B12408@cc.usu.edu>
	<20010418164436.A41431@ilse.nl>
	<20010418085424.A13383@cc.usu.edu>
	<20010418173727.A5021@rakete.joerdens.de>
	<20010418202814.B16143@ilse.nl>

On Wed, Apr 18, 2001 at 08:28:14PM +0200, Mathijs Brands wrote:
 
> I've seen both MySQL and PostgreSQL give up (MySQL just hung, pgsql
> cored) when I tried simple selects from a couple of hundred concurrent
> connections; no transactions or other fancy stuff there. I think I was
> using MySQL 3.22.?? and pgsql 6.5.3, so more modern versions may well be
> able to cope with these numbers of connections. It's been more than a
> year since I last tried it.

	I can see that happenning in 6.5, but not in later versions. 
 
> I don't know what the current state of affairs is, but it is my
> understanding that, while pgsql performs admirably on tasks which mostly
> read data, pgsql isn't really able to cope (performance wise) with an
> application that has a very high insert to select ratio, such as OLTP.
> I'm looking into using pgsql to for implementing datamarts for a CRM
> application, so I'll so how that goes in the next couple of weeks. I'm
> keeping my fingers crossed ;)

	I think you got that backwards. PG is the one who can deal with OLTP
well. MySQL with its pessimistic locking model just hangs forever. Take a
look at Tim Perdue's tests with SourceForge on phpbuilder.com
 
> The reason for the previous paragraph is that I think pgsql (PHP even
> more so) is mosty used for databases in which the insert to select ratio
> is much more favourable. But hey, that's my opinion.

	Another misconception. Unless your site is very very simple, you have
_plenty_ of INSERTs and UPDATEs. On my sites, _every_ http request
requires at least 2 SELECTs and 1 INSERT, plus all the other stuff they
are doing. That's so I can keep track of who is visiting what. On MySQL
this would be unbearable.

	-Roberto

-- 
+----| http://fslc.usu.edu USU Free Software & GNU/Linux Club |------+
  Roberto Mello - Computer Science, USU - http://www.brasileiro.net 
       http://www.sdl.usu.edu - Space Dynamics Lab, Developer    
All true wisdom is found in taglines.



view thread (5+ messages)  latest in thread

Message-ID: <20010420103645.B20153@cc.usu.edu>
Permalink:  ../20010420103645.B20153@cc.usu.edu/
Also on:    postgresql.org/message-id/20010420103645.B20153@cc.usu.edu

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: rmello@cc.usu.edu, mathijs@ilse.nl, frank@joerdens.de, pgsql-php@postgresql.org
  Subject: Re: persistent connections, AOLserver (Was: [SQL] maybe Offtopic : PostgreSQL & PHP ?)
  In-Reply-To: <20010420103645.B20153@cc.usu.edu>

* 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