pg.ddx.io pgsql-performance@postgresql.org mailing list archive
help / color / mirror / Atom feed From: Joshua D. Drake <jd@commandprompt.com>
To: Hervé Piedvache <herve@elma.fr>
Cc: pgsql-performance@postgresql.org
Subject: Re: PostgreSQL clustering VS MySQL clustering
Date: Thu, 20 Jan 2005 06:44:16 -0800
Message-ID: <41EFC3C0.6080903@commandprompt.com> (raw )
In-Reply-To: <200501201503.31241.herve@elma.fr >
References: <200501201503.31241.herve@elma.fr >
Hervé Piedvache wrote:
>Dear community,
>
>My company, which I actually represent, is a fervent user of PostgreSQL.
>We used to make all our applications using PostgreSQL for more than 5 years.
>We usually do classical client/server applications under Linux, and Web
>interface (php, perl, C/C++). We used to manage also public web services with
>10/15 millions records and up to 8 millions pages view by month.
>
>
Depending on your needs either:
Slony: www.slony.info
or
Replicator: www.commandprompt.com
Will both do what you want. Replicator is easier to setup but
Slony is free.
Sincerely,
Joshua D. Drake
>Now we are in front of a new need, but we do not find any good solution with
>PostgreSQL.
>We need to make a sort of directory of millions of data growing about 4/8
>millions per month, and to be able to be used by many users from the web. In
>order to do this, our solution need to be able to run perfectly with many
>insert and many select access (done before each insert, and done by web site
>visitors). We will also need to make a search engine for the millions of data
>(140/150 millions records at the immediate beginning) ... No it's not google,
>but the kind of volume of data stored in the main table is similar.
>
>Then ... we have made some tests, with the actual servers we have here, like a
>Bi-Pro Xeon 2.8 Ghz, with 4 Gb of RAM and the result of the cumulative
>inserts, and select access is slowing down the service really quickly ...
>(Load average is going up to 10 really quickly on the database).
>
>We were at this moment thinking about a Cluster solution ... We saw on the
>Internet many solution talking about Cluster solution using MySQL ... but
>nothing about PostgreSQL ... the idea is to use several servers to make a
>sort of big virtual server using the disk space of each server as one, and
>having the ability to use the CPU and RAM of each servers in order to
>maintain good service performance ...one can imagin it is like a GFS but
>dedicated to postgreSQL...
>
>Is there any solution with PostgreSQL matching these needs ... ?
>Do we have to backport our development to MySQL for this kind of problem ?
>Is there any other solution than a Cluster for our problem ?
>
>Looking for your reply,
>
>Regards,
>
>
--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-667-4564 - jd@commandprompt.com - http://www.commandprompt.com
PostgreSQL Replicator -- production quality replication for PostgreSQL
Attachments:
jd.vcf (text/x-vcard, 283B) download
begin:vcard
fn:Joshua Drake
n:Drake;Joshua
org:Command Prompt, Inc.
adr:;;PO Box 215 ;Cascade Locks;OR;97014;US
email;internet:jd@commandprompt.com
title:Consultant
tel;work:503-667-4564
tel;fax:503-210-0334
x-mozilla-html:FALSE
url:http://www.commandprompt.com
version:2.1
end:vcard
view thread (131+ messages) latest in thread
Message-ID: <41EFC3C0.6080903@commandprompt.com>
Permalink: ../41EFC3C0.6080903@commandprompt.com/
Also on: postgresql.org/message-id/41EFC3C0.6080903@commandprompt.com
copy link · copy postgr.es
reply 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: jd@commandprompt.com, herve@elma.fr
Subject: Re: PostgreSQL clustering VS MySQL clustering
In-Reply-To: <41EFC3C0.6080903@commandprompt.com>
* 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