Just got my second SSD. How should I split up my DB?

PostgreSQL is the database server used to store information. Do you have a question or are you having problem with PostgreSQL? If so, post them here.

Moderator: Moderators

Just got my second SSD. How should I split up my DB?

Postby bloodndef » Sat Aug 21, 2010 2:20 am

I've read the threads on performance tuning and feel comfortable with it for the most part. I'm presently using a symbolic link on the logs and am comfortable with that.

I have a 50GB SSD running my OS with about 20GB free:
http://www.newegg.com/Product/Product.a ... -_-Product
I also now have a 128GB SSD
http://www.newegg.com/Product/Product.a ... 8GB%20M225
and 2 TB HDDs:
http://www.newegg.com/Product/Product.a ... -_-Product

My database is 60GB now and never exceeds 80GB.

I'm going to uninstall and reinstall EVERYTHING on a clean system. For best performance, how would you install PostgreSQL and PT3 based on my hard drive situation? I'm guessing I'm going to get the best performance using the SSDs only - and have the HDDs for storage and backup. Without any advice, I would have PT3 and logs on the 50GB OS drive and database tables on the 128GB SSD... but perhaps there's another configuration that will do me better.

Thanks for any advice!
bloodndef
 
Posts: 99
Joined: Fri Feb 27, 2009 1:28 am

Re: Just got my second SSD. How should I split up my DB?

Postby tarix » Sat Aug 21, 2010 5:07 am

bloodndef wrote:Without any advice, I would have PT3 and logs on the 50GB OS drive and database tables on the 128GB SSD... but perhaps there's another configuration that will do me better.


That's precisely what I would do. I would also install postgres in such a way that only the data folder lives on the second SSD and the executables and all that stay on your OS SSD. Also I would make sure your pg_log and maybe even the pg_xlog is hitting the OS drive and not the postgres drive.

To be honest I'm a little torn on where the pg_xlog should really go in an SSD. On one hand you have lots of little activity on your OS drive (swapfiles, hand histories, etc.) and on the other hand you want to keep your postgres drive as "open" as possible for imports and queries.
tarix
Developer
 
Posts: 3760
Joined: Tue May 20, 2008 2:49 pm

Re: Just got my second SSD. How should I split up my DB?

Postby bloodndef » Sun Aug 22, 2010 2:24 pm

Thanks for the input!

I thought of one thing though: does it matter where my "Processed Files" are stored? I've got them going to one of the TB HDDs. Is this operation so small that it won't really make a performance difference or should I have Processed Files be stored on the OS SSD or Database SSD?
bloodndef
 
Posts: 99
Joined: Fri Feb 27, 2009 1:28 am

Re: Just got my second SSD. How should I split up my DB?

Postby WhiteRider » Sun Aug 22, 2010 3:18 pm

Processed files are only moved when you stop auto import, so this doesn't really have any effect on performance. I'd suggest keeping them separate from the main data drives as they are only needed for backup.
WhiteRider
Moderator
 
Posts: 54017
Joined: Sat Jan 19, 2008 7:06 pm
Location: UK

Re: Just got my second SSD. How should I split up my DB?

Postby bloodndef » Sun Aug 22, 2010 3:46 pm

Good to know, thank you!

So far, there is a nice performance boost using 2 SSDs. :)
bloodndef
 
Posts: 99
Joined: Fri Feb 27, 2009 1:28 am


Return to PostgreSQL [Read Only]

Who is online

Users browsing this forum: No registered users and 28 guests

cron
highfalutin