Re: Partitioning / Clustering

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: Partitioning / Clustering
Date: 2005-05-12 17:33:41
Message-ID: 200505121033.41254.josh@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

People,

> In general I think your point is valid. Just remember that it probably
> also matters how you count page views. Because technically images are a
> separate page (and this thread did discuss serving up images). So if
> there are 20 graphics on a specific page, that is 20 server hits just
> for that one page.

Also, there's bots and screen-scrapers and RSS, web e-mails, and web services
and many other things which create hits but are not "people". I'm currently
working on clickstream for a site which is nowhere in the top 100, and is
getting 3 million real hits a day ... and we know for a fact that at least
1/4 of that is bots.

Regardless, the strategy you should be employing for a high traffic site is
that if your users hit the database for anything other than direct
interaction (like filling out a webform) then you're lost. Use memcached,
squid, lighttpd caching, ASP.NET caching, pools, etc. Keep the load off the
database except for the stuff that only the database can do.

--
Josh Berkus
Aglio Database Solutions
San Francisco

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Alex Stapleton 2005-05-12 17:45:32 Re: Partitioning / Clustering
Previous Message Josh Berkus 2005-05-12 17:25:41 Re: tuning Postgres for large data import (using Copy from)