-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 09/11/07 07:55, Phoenix Kiula wrote: > On 11/09/2007, Franz.Rasper@xxxxxx <Franz.Rasper@xxxxxx> wrote: >> It depends what you want to do with your database. >> >> Do you have many reads (select) or a lot of writes (update,insert) ? > > > This one will be a hugely INSERT thing, very low on UPDATEs. The > INSERTS will have many TEXT fields as they are free form data. So the > database will grow very fast. Size will grow pretty fast too. 15000 rows/day times 365 days = 5475000 rows. How big are these rows? *That* is the crucial question. >> You should use a hardware raid controller with battery backup write cache >> (write cache should be greater than 256 MB). > > > I'll have a raid controller in both scenarios, but which RAID should > be better: RAID1 or RAID10? The striping aspects of RAID10 makes sequential reads and writes and large writes much faster. The more spindles you have, the faster it is. If you are *really* concerned about speed, 4 x 147GB 10K SCSI >> How much memory do you have ? > > > 4GB to begin with.. > > >> How big is your database, tables ... ? > > > Huge, as the two main tables will each have about ten TEXT columns > each. They will have about 15000 new entries every day, which is quite > a load, so I believe we will have to partition it at least by month > but even so it will grow at a huge pace. 15000 in an 8 hour window is 31.25 inserts/minute or ~2 seconds/insert. If the records are 30MB each, then that could cause some stress on the system in that 8 hour window. If they are 3MB each, not a chance. > While we are at it, would postgres be any different in performance > across a single-CPU Quad Core Xeon with a dual CPU dual-core AMD > Opteron? Or should the hard disk and RAM be the major considerations > as usually proposed? Opteron is the standard answer. What is your backup/recovery strategy? - -- Ron Johnson, Jr. Jefferson LA USA Give a man a fish, and he eats for a day. Hit him with a fish, and he goes away for good! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG5pn1S9HxQb37XmcRAnl1AJ48p5CGBMma15yWt9FtD0bOXN/D7ACeNxxq 9EWbm10L/Zt/tB1xPly/Ex0= =QPI1 -----END PGP SIGNATURE----- ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster
