From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | Dave Page <dpage(at)postgresql(dot)org> |
Cc: | Alexander Staubo <alex(at)purefiction(dot)net>, PFC <lists(at)peufeu(dot)com>, Scott Ribe <scott_ribe(at)killerbytes(dot)com>, Naz Gassiep <naz(at)mira(dot)net>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Integrity on large sites |
Date: | 2007-05-24 16:07:21 |
Message-ID: | 4655B839.60409@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Dave Page wrote:
>> problem with your setup. Granted, MySQL is a pretty bad database, but
>> it's not *that* bad -- your example implies that heavily MyISAM-based
>> (you don't say whether this is MyISAM or InnoDB) sites such as
>> Slashdot and Flickr should be falling over every hour.
>
> I'm not going to comment on who's fault it is, but the OP quoted 100
> updates and 600 selects per *second*. I can't imagine Flickr or Slashdot
> (which is heavily csched for reading) are under anything like that sort
> of constant load.
Uhmmm.... I would not be surprised at *all* at slashdot or flickr doing
that type of velocity. We have customers right now that under peak are
doing 10 times that and yes these are customers that have similar types
of websites.
Sincerely,
Joshua D. Drake
>
> Regards, Dave.
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
>
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
From | Date | Subject | |
---|---|---|---|
Next Message | Teodor Sigaev | 2007-05-24 16:22:04 | Re: Postgresql 8.2.4 crash with tsearch2 |
Previous Message | Martijn van Oosterhout | 2007-05-24 16:06:11 | Re: Very big transaction in a stored procedure : how can i commit in the middle of it ? |