pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Joshua D. Drake <jd@commandprompt.com>
To: Stephen Frost <sfrost@snowman.net>
Cc: Hervé Piedvache <herve@elma.fr>
Cc: pgsql-performance@postgresql.org
Subject: Re: PostgreSQL clustering VS MySQL clustering
Date: Thu, 20 Jan 2005 06:49:56 -0800
Message-ID: <41EFC514.9090806@commandprompt.com> (raw)
In-Reply-To: <20050120144416.GO10437@ns.snowman.net>
References: <200501201503.31241.herve@elma.fr>
	<20050120143045.GN10437@ns.snowman.net>
	<200501201539.49874.herve@elma.fr>
	<20050120144416.GO10437@ns.snowman.net>

Stephen Frost wrote:

>* Herv? Piedvache (herve@elma.fr) wrote:
>  
>
>>Le Jeudi 20 Janvier 2005 15:30, Stephen Frost a écrit :
>>    
>>
>>>* Herv? Piedvache (herve@elma.fr) wrote:
>>>      
>>>
>>>>Is there any solution with PostgreSQL matching these needs ... ?
>>>>        
>>>>
>>>You might look into pg_pool.  Another possibility would be slony, though
>>>I'm not sure it's to the point you need it at yet, depends on if you can
>>>handle some delay before an insert makes it to the slave select systems.
>>>      
>>>
>>I think not ... pgpool or slony are replication solutions ... but as I have 
>>said to Christopher Kings-Lynne how I'll manage the scalabilty of the 
>>database ? I'll need several servers able to load a database growing and 
>>growing to get good speed performance ...
>>    
>>
>
>They're both replication solutions, but they also help distribute the
>load.  For example:
>
>pg_pool will distribute the select queries amoung the servers.  They'll
>all get the inserts, so that hurts, but at least the select queries are
>distributed.
>
>slony is similar, but your application level does the load distribution
>of select statements instead of pg_pool.  Your application needs to know
>to send insert statements to the 'main' server, and select from the
>others.
>  
>
You can put pgpool in front of replicator or slony to get load
balancing for reads.

>  
>
>>>>Is there any other solution than a Cluster for our problem ?
>>>>        
>>>>
>>>Bigger server, more CPUs/disks in one box.  Try to partition up your
>>>data some way such that it can be spread across multiple machines, then
>>>if you need to combine the data have it be replicated using slony to a
>>>big box that has a view which joins all the tables and do your big
>>>queries against that.
>>>      
>>>
>>But I'll arrive to limitation of a box size quickly I thing a 4 processors 
>>with 64 Gb of RAM ... and after ?
>>    
>>
Opteron.


>
>Go to non-x86 hardware after if you're going to continue to increase the
>size of the server.  Personally I think your better bet might be to
>figure out a way to partition up your data (isn't that what google
>does anyway?).
>
>	Stephen
>  
>


-- 
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: <41EFC514.9090806@commandprompt.com>
Permalink:  ../41EFC514.9090806@commandprompt.com/
Also on:    postgresql.org/message-id/41EFC514.9090806@commandprompt.com

 · 

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, sfrost@snowman.net, herve@elma.fr
  Subject: Re: PostgreSQL clustering VS MySQL clustering
  In-Reply-To: <41EFC514.9090806@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