Skip site navigation (1) Skip section navigation (2)

Re: Decide between Postgresql and Mysql (help of

From: "Craig A(dot) James" <cjames(at)modgraph-usa(dot)com>
To: Gorshkov <listsubscriptions(at)oghma(dot)on(dot)ca>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Decide between Postgresql and Mysql (help of
Date: 2006-03-30 03:01:26
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
This is off-topic for this group so I'll just give a brief reply; I'm happy to carry on more just between the two of us...

Gorshkov wrote:
> That being said ..... what *is* the difference between coding a website - 
> major or otherwise - in an "old-fashioned" compiled language and a 
> non-compiled language, except for the amount of hoursepower and memory you 
> require?
> Old-fashioned doesn't mean bad, inappropriate, or inferior. It's just not the 
> latest-and-greatest, however it's currently defined by the geek fashion 
> police.

Our experience coding web sites with C/C++ versus Perl is about a factor of ten in productivity.  We only use C/C++ for CPU-intensive calculations, such as scientific prediction code.  Everything else is Perl or Java.

I recently re-coded 10,000 lines of C into 650 lines of Perl.  Why?  String handling, hash tables, and the simplicity of DBD/DBI.  And there was no loss of performance, because the app was strictly I/O bound (that is, Postgres was I/O bound).  Sure, the old app may not have been optimal, but we're talking about a factor of 15 reduction in lines of code.

That's not "geek fashion", it's good engineering.  Pick the best tool for the job, and learn how to use it.


In response to


pgsql-performance by date

Next:From: Brendan DuddridgeDate: 2006-03-30 03:12:28
Subject: Query using SeqScan instead of IndexScan
Previous:From: Craig A. JamesDate: 2006-03-30 02:23:52
Subject: Re: Decide between Postgresql and Mysql (help of

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group