pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Dave Cramer <pg@fastcrypt.com>
To: Steinar H. Gunderson <sgunderson@bigfoot.com>
Cc: postgresql performance list <pgsql-performance@postgresql.org>
Subject: Re: Postgres vs. MySQL
Date: Thu, 25 Nov 2004 07:38:23 -0500
Message-ID: <41A5D23F.3020705@fastcrypt.com> (raw)
In-Reply-To: <20041124162614.GB30845@uio.no>
References: <1101302058.338.74.camel@haddock.cmima.csic.es>
	<Pine.LNX.4.61.0411240908400.22359@leda.steelsun.com>
	<20041124162614.GB30845@uio.no>

I did some work on RT wrt Postgres for a company and found that their 
was lots of room for improvement
particularly if you are linking requests. The latest RT code hopefully 
has fixes as a result of this work.

Dave

Steinar H. Gunderson wrote:

>On Wed, Nov 24, 2004 at 09:57:52AM -0500, Christian Fowler wrote:
>  
>
>>As for performance, lots of others will probably volunteer tips and 
>>techniques. In my experience, properly written and tuned applications will 
>>show only minor speed differences. I have seen several open-source apps 
>>that "support postgres" but are not well tested on it. Query optimization 
>>can cause orders of magnitude performance differences.
>>    
>>
>
>Definitely. My favourite is Request Tracker (we use 2.x, although 3.x is the
>latest version), which used something like 5-600 queries (all seqscans since
>the database schema only had an ordinary index on the varchar fields in
>question, and the queries were automatically searching on LOWER(field) to
>emulate MySQL's case-insensitivity on varchar fields) for _every_ page shown.
>Needless to say, the web interface was dog slow -- some index manipulation
>and a few bugfixes (they had some kind of cache layer which would eliminate
>98% of the queries, but for some reason was broken for non-MySQL databases)
>later, and we were down to 3-4 index scans, a few orders of magnitude faster.
>:-)
>
>/* Steinar */
>  
>

-- 
Dave Cramer
http://www.postgresintl.com
519 939 0336
ICQ#14675561




view thread (12+ messages)  latest in thread

Message-ID: <41A5D23F.3020705@fastcrypt.com>
Permalink:  ../41A5D23F.3020705@fastcrypt.com/
Also on:    postgresql.org/message-id/41A5D23F.3020705@fastcrypt.com

 · 

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-performance@postgresql.org
  Cc: pg@fastcrypt.com, sgunderson@bigfoot.com
  Subject: Re: Postgres vs. MySQL
  In-Reply-To: <41A5D23F.3020705@fastcrypt.com>

* 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