Re: PostgreSQL clustering VS MySQL clustering

Two way xeon's are as fast as a single opteron, 150M rows isn't a big deal.
Clustering isn't really the solution, I fail to see how clustering
actually helps since it has to slow down file access.

Dave

Hervé Piedvache wrote:

>Le Jeudi 20 Janvier 2005 19:09, Bruno Almeida do Lago a écrit :
>
>
>>Could you explain us what do you have in mind for that solution? I mean,
>>forget the PostgreSQL (or any other database) restrictions and explain us
>>how this hardware would be. Where the data would be stored?
>>
>>I've something in mind for you, but first I need to understand your needs!
>>
>>
>
>I just want to make a big database as explained in my first mail ... At the
>beginning we will have aprox. 150 000 000 records ... each month we will add
>about 4/8 millions new rows in constant flow during the day ... and in same
>time web users will access to the database in order to read those data.
>Stored data are quite close to data stored by google ... (we are not making a
>google clone ... just a lot of data many small values and some big ones ...
>that's why I'm comparing with google for data storage).
>Then we will have a search engine searching into those data ...
>
>Dealing about the hardware, for the moment we have only a bi-pentium Xeon
>2.8Ghz with 4 Gb of RAM ... and we saw we had bad performance results ... so
>we are thinking about a new solution with maybe several servers (server
>design may vary from one to other) ... to get a kind of cluster to get better
>performance ...
>
>Am I clear ?
>
>Regards,
>
>

--
Dave Cramer
http://www.postgresintl.com
519 939 0336
ICQ#14675561