Re: Separate volumes

With SSD and it's random IO performance, I doubt that this advice would
apply as much, and adds complexity to your configuration and management.
In particular if you use any filesystem level snapshotting (like with ZFS),
splitting the filespaces will make it harder to do restores and using
snapshots.

On Mon, Apr 6, 2020 at 10:40 AM Ed Behn <ed(dot)behn(at)collins(dot)com> wrote:

> I was once told that it's best practice to store tables and indexes in
> separate tablespaces located on separate physical drives. It seemed logical
> that this should improve performance because the read-head wouldn't need to
> jump back and forth between a table and its index.
>
> However, I can't seem to find this advice anywhere online. Is it indeed
> best practice? Is it worth the hassle?
>
> -Ed
>
> Ed Behn | Senior Systems Engineer | Avionics
>
> COLLINS ÆROSPACE
>
> 2551 Riva Road, Annapolis, MD 21401 USA
>
> Tel: +1 410 266 4426 | Mobile: +1 240 696 7443
>
> ed(dot)behn(at)collins(dot)com | collinsaerospace.com
>
> CONFIDENTIALITY WARNING: This message may contain proprietary and/or
> privileged information of Collins Aerospace and its affiliated companies.
> If you are not the intended recipient, please 1) Do not disclose, copy,
> distribute or use this message or its contents. 2) Advise the sender by
> return email. 3) Delete all copies (including all attachments) from your
> computer. Your cooperation is greatly appreciated.
>
>

--
*Erik Brandsberg*
erik(at)heimdalldata(dot)com

www.heimdalldata.com
+1 (866) 433-2824 x 700
[image: AWS Competency Program]
<https://aws.amazon.com/partners/find/partnerdetails/?n=Heimdall%20Data&id=001E000001d9pndIAA>