Re: Mounting a data dir read only

From: "Chad Wagner" <chad(dot)wagner(at)gmail(dot)com>
To: Thorsten Körner <t(dot)koerner(at)cappuccinosoft(dot)de>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Mounting a data dir read only
Date: 2007-01-16 23:38:06
Message-ID: 81961ff50701161538o41376afcnf9f1deec6334be46@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 1/16/07, Thorsten Körner <t(dot)koerner(at)cappuccinosoft(dot)de> wrote:
>
> The projects Website is a very high traffic site, with about 500 Pi /
> sec. we
> are facing performance trouble, when using just one server.
> Searches etc. we have implemented using lucene on our backend servers, to
> keep
> the database alive, but since content is very dynamic, there is need to
> update lucene indexes very often.
> Another problem are some logs, like counters how often users have seen the
> pages with contents or userprofiles etc.
> All those things, seems to me very difficulty to implement with slony.
> Do you have a hint, which way we can go?
>

Perhaps you need to look at a different solution. It is apparent you want
to reduce I/O and activity on the database, have you looked at distributed
caches like memcached (http://www.danga.com/memcached/) ?

Many popular high volume websites are using memcached (Wikipedia, Slashdot,
Live Journal, etc.).

--
Chad
http://www.postgresqlforums.com/

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Harpreet Dhaliwal 2007-01-17 00:15:50 Re: Dynamic loading of Perl Code in Postgres functions
Previous Message Chad Wagner 2007-01-16 23:30:00 Re: invalid byte sequence for encoding "UTF8"