From: PFC <lists@boutiquenumerique.com>
To: Alex Stapleton <alexs@advfn.com>
Cc: josh@agliodbs.com, "David Roussel" <pgsql-performance@diroussel.xsmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Partitioning / Clustering
Date: Thu, 12 May 2005 12:09:34 +0200
Message-ID: <op.sqnqh8pyth1vuj@localhost> (raw)
In-Reply-To: <1115798277.29223.233869472@webmail.messagingengine.com>
References: <5F94B6EB-3925-4CD3-A67F-4310890B438A@advfn.com>
<1115798277.29223.233869472@webmail.messagingengine.com>
<200505111013.52067.josh@agliodbs.com>
<op.sqmuc2nnth1vuj@localhost>
<C5F910FB-A695-4070-A8FF-2DB576426846@advfn.com>
> machines. Which has it's own set of issues entirely. I am not entirely
> sure that memcached actually does serialize data when it's comitted into
I think it does, ie. it's a simple mapping of [string key] => [string
value].
> memcached either, although I could be wrong, I have not looked at the
> source. Certainly if you can ensure that a client always goes back to
> the same machine you can simplify the whole thing hugely. It's generally
> not that easy though, you need a proxy server of some description
> capable of understanding the HTTP traffic and maintaining a central
Yes...
You could implement it by mapping servers to the hash of the user session
id.
Statistically, the servers would get the same numbers of sessions on each
of them, but you have to trust statistics...
It does eliminate the lookup table though.
> idea, I would like to hear a way of implementing them cheaply (and on
> PHP) as well. I may have to give that some thought in fact. Oh yeah, and
> load balancers software often sucks in annoying (if not always
> important) ways.
You can use lighttpd as a load balancer, I believe it has a stick
sessions plugin (or you could code one in, it's open source after all). It
definitely support simple round-robin load balancing, acting as a proxy to
any number of independent servers.
>> matter, it's pretty impressive. The google filesystem has nothing to do
>> with databases though, it's more a massive data store / streaming
>> storage.
>
> Since when did Massive Data stores have nothing to do with DBs? Isn't
> Oracle Cluster entirely based on forming an enormous scalable disk array
> to store your DB on?
Um, well, the Google Filesystem is (like its name implies) a filesystem
designed to store huge files in a distributed and redundant manner. Files
are structured as a stream of records (which are themselves big in size)
and it's designed to support appending records to these stream files
efficiently and without worrying about locking.
It has no querying features however, that is why I said it was not a
database.
I wish I could find the whitepaper, I think the URL was on this list some
day, maybe it's on Google's site ?
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: lists@boutiquenumerique.com, alexs@advfn.com, pgsql-performance@diroussel.xsmail.com
Subject: Re: Partitioning / Clustering
In-Reply-To: <op.sqnqh8pyth1vuj@localhost>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox