Re: MySQL vs postgres

["imago" <imago@xxxxxxxxxxx>]

> Web applications typically have a high ratio of reading to
writing.
> Issues like table locking and transactions affect write speed and
> complexity more than reads.  Even a site like Slashdot, which has
busy
> discussion forums, does SELECT a lot more than INSERT.
>
In my application, the $ hits are the bids.  Yes there are many more
read than these $ writes but the bids are more complex transactions
with a number of commands and calculations involved for each one.

> on the web,
> anything goes:  it's not unusual for spikes in traffic to be 100
or
> 1000 times your site's normal load.  Those are precisely the times
> when it's both most important and most difficult that your
software
> have good performance.

This is when the most $ is made by the system. Customer to customer
auctions have definite "rush" hours.  These times are explioted by
savy listers for their auction end times. Users only see the slow
response and get mad when they loose the chance to be in the action.

 Building that speed buffer isn't cheap, and
> at high performance levels, a severalfold speedup in software can
> save a great deal of money in hardware.

I am trying to work with Linux software systems for the
efficiency/cost gain over other syatems for an undercapitalized
startup.  I now see postres is an important link in the chain.

imago