Page 1 of 1

Optimal setup across drives/network?

PostPosted: Fri May 16, 2008 12:07 pm
by fooz
I'm trying to figure out the optimal application/DB configuration from a performance, scalability, and portability perspective. I'm technically savvy and willing to dig in to whatever in order to achieve the ideal.

In a separate post, _dave_ said:

"Heavy" users should not install Postgres to a seperate drive (or array) - they should install Postgres to "Program Files" like any other user, and initialise the cluster on their other drives. That or ideally (unless the "Program Files" drive is shockingly slow) use tablespace to store *data only* on the fast / large disk(s).


I have a similar setup to the OP of this thread, with a smaller older internal drive and a new, massive 1 TB external drive (connected via USB). I also have 2 other networked computers that will access this data. Some questions:

1) Why should we install PostGres to "Program files" or the main "c:" drive and the *data only* to the fast / large disk? Obviously I want to install the data on the larger external drive, but what is the advantage of putting the PostGres (application?) on the main drive? Given the external drive is connected via USB, I imagine the access time is faster to the internal drive.

2) Also, how portable would this configuration be? Could I unplug the external drive, and plug it into my laptop and access all of the same data?

thanks,
fooz

Re: Optimal setup across drives/network?

PostPosted: Sat May 17, 2008 6:01 pm
by fooz
bump

Re: Optimal setup across drives/network?

PostPosted: Mon May 19, 2008 2:49 pm
by APerfect10
fooz wrote:1) Why should we install PostGres to "Program files" or the main "c:" drive and the *data only* to the fast / large disk? Obviously I want to install the data on the larger external drive, but what is the advantage of putting the PostGres (application?) on the main drive? Given the external drive is connected via USB, I imagine the access time is faster to the internal drive.


The size of your hard drive is not the important part, the speed of it is. I would not recommend installing a PostgreSQL database on a hard drive anything less than 7200RPM. In dave's post, he was speaking about using a tablespace on a separate internal drive via SATA, etc. I am not sure if using a drive connected via USB will render the same performance gains or not. You would still benefit from the data on the external drive but the networking speed may make it negligent.

2) Also, how portable would this configuration be? Could I unplug the external drive, and plug it into my laptop and access all of the same data?


Good question and I'm not that sure. Dave would really be better to answer your questions. I think there should be a way to make it portable although it will be a little cumbersome.

Best regards,

Derek