Re: [PERFORM] Migrating to Postgresql and new hardware

2011-01-31 Thread Lars
: Greg Smith [mailto:g...@2ndquadrant.com] Skickat: den 29 januari 2011 01:27 Till: Lars Kopia: mark; pgsql-performance@postgresql.org Ämne: Re: [PERFORM] Migrating to Postgresql and new hardware Lars wrote: > Below is a quote from the Pliant datasheet: > "No Write Cache: > Plian

Re: [PERFORM] Migrating to Postgresql and new hardware

2011-01-28 Thread Greg Smith
Lars wrote: Below is a quote from the Pliant datasheet: "No Write Cache: Pliant EFDs deliver outstanding write performance without any dependence on write cache and thus does not use battery/supercap." I liked the article The Register wrote about them, with the headline "Pliant's SSDs are a

Re: [PERFORM] Migrating to Postgresql and new hardware

2011-01-20 Thread Scott Marlowe
On Thu, Jan 20, 2011 at 7:48 AM, Andy Colson wrote: > Or... PG is just so good we've never had to use more than one database > server!  :-) Hehe, while you can do a lot with one server, there are some scenarios where sharding is the answer. I have a horror story about not sharding when we shoul

Re: [PERFORM] Migrating to Postgresql and new hardware

2011-01-20 Thread Andy Colson
On 1/19/2011 6:42 PM, Craig Ringer wrote: On 01/19/2011 05:09 PM, Lars wrote: Thanks for the reply! As others have mentioned, how are you going to be doing your "shards"? Hmm... shards might not have been a good word to describe it. I'll paste what I wrote in another reply: I used sharding a

Re: [PERFORM] Migrating to Postgresql and new hardware

2011-01-19 Thread Craig Ringer
On 01/19/2011 05:09 PM, Lars wrote: Thanks for the reply! MyISAM was chosen back in 2000. I'm not aware of the reasoning behind this choice... Dell claims both the Samsung and the Pliant are safe to use. Below is a quote from the Pliant datasheet: "No Write Cache: Pliant EFDs deliver outstandi

Re: [PERFORM] Migrating to Postgresql and new hardware

2011-01-19 Thread Lars
database servers. There are some shared data that is stored in a special "shared" database. /Lars -Ursprungligt meddelande- Från: mark [mailto:dvlh...@gmail.com] Skickat: den 19 januari 2011 05:10 Till: Lars Kopia: pgsql-performance@postgresql.org Ämne: RE: [PERFORM] Migrating to Po

Re: [PERFORM] Migrating to Postgresql and new hardware

2011-01-19 Thread Lars
> Are you going to RAID the SSD drives at all? Yes, I was thinking four drives in RAID 10 and a (hot) spare drive... > Of course this is based on my experience, and I have my fireproof suit since > I mentioned the word fusionIO :) Hehe FusionIO has some impressive stats! SSD in RAID10 provides r

Re: [PERFORM] Migrating to Postgresql and new hardware

2011-01-19 Thread Lars
> No idea what mysql thinks a shard is, but in PG we have read-only hot > standby's. I used sharding as an expression for partitioning data into several databases. Each user in the system is unaware of any other user. The user never accesses the private data of another user. Each user could in th

Re: [PERFORM] Migrating to Postgresql and new hardware

2011-01-18 Thread Scott Marlowe
On Tue, Jan 18, 2011 at 3:56 AM, Lars wrote: > Any comments on the setups? How would an alternative with 15K disks (6 RAID > 10 + 1 spare, or even 10 RAID10 + 1 spare) compare? RAID-10 is going to trounce RAID-5 for writes, which is where you usually have the most issues. > How would these alt

Re: [PERFORM] Migrating to Postgresql and new hardware

2011-01-18 Thread Craig Ringer
On 18/01/11 18:56, Lars wrote: > Hi, > > We are in the process of moving a web based application from a MySql to > Postgresql database. > Our main reason for moving to Postgresql is problems with MySql (MyISAM) > table locking. > We will buy a new set of servers to run the Postgresql databases.

Re: [PERFORM] Migrating to Postgresql and new hardware

2011-01-18 Thread mark
l.org > Subject: [PERFORM] Migrating to Postgresql and new hardware > > Hi, > > We are in the process of moving a web based application from a MySql to > Postgresql database. > Our main reason for moving to Postgresql is problems with MySql > (MyISAM) table locking. I would neve

Re: [PERFORM] Migrating to Postgresql and new hardware

2011-01-18 Thread Mark Felder
On Tue, 18 Jan 2011 16:06:17 -0600, Strange, John W wrote: Of course this is based on my experience, and I have my fireproof suit since I mentioned the word fusionIO :) I'll throw a fire blanket up as well. We have a customer who has been running Fusion IO with Postgres for about 2 years

Re: [PERFORM] Migrating to Postgresql and new hardware

2011-01-18 Thread Strange, John W
d the word fusionIO :) - John -Original Message- From: pgsql-performance-ow...@postgresql.org [mailto:pgsql-performance-ow...@postgresql.org] On Behalf Of Lars Sent: Tuesday, January 18, 2011 4:57 AM To: pgsql-performance@postgresql.org Subject: [PERFORM] Migrating to Postgresql an

Re: [PERFORM] Migrating to Postgresql and new hardware

2011-01-18 Thread Andy Colson
oops, call them database 'a' and database 'b'. -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance

Re: [PERFORM] Migrating to Postgresql and new hardware

2011-01-18 Thread Andy Colson
On 1/18/2011 4:56 AM, Lars wrote: Hi, We are in the process of moving a web based application from a MySql to Postgresql database. Our main reason for moving to Postgresql is problems with MySql (MyISAM) table locking. We will buy a new set of servers to run the Postgresql databases. The curren

[PERFORM] Migrating to Postgresql and new hardware

2011-01-18 Thread Lars
Hi, We are in the process of moving a web based application from a MySql to Postgresql database. Our main reason for moving to Postgresql is problems with MySql (MyISAM) table locking. We will buy a new set of servers to run the Postgresql databases. The current setup is five Dell PowerEdge 295