MIME-Version: 1.0
From: Wells Oliver <wells.oliver@gmail.com>
Date: Tue, 5 Oct 2021 15:06:59 -0700
Message-ID: 
 <CAOC+FBUWjYqef5KOCcSh4OUi7d2EcStMTgwt6jJwGeChGRvopA@mail.gmail.com>
Subject: Pros/cons of big databases vs smaller databases and RDS
To: pgsql-admin <pgsql-admin@postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000c9009605cda2415d"
Archived-At: 
 <https://www.postgresql.org/message-id/CAOC%2BFBUWjYqef5KOCcSh4OUi7d2EcStMTgwt6jJwGeChGRvopA%40mail.gmail.com>
Precedence: bulk

--000000000000c9009605cda2415d
Content-Type: text/plain; charset="UTF-8"

Hi-- to keep it short, I feel like I've generally heard the larger your DB
is, the less efficient it might run, likely due to disk I/O. Maybe I'm
terribly mistaken in this perception.

We have two DBs, one primarily accessed by humans and systems, which is
~1TB in size, and aggregates most of what we store in raw, longer format on
a second DB that is about ~6TB in size.

As we consider plans to migrate to RDS, we've talked a lot about
combining the two as more and more the case is querying the larger DB and
wanting data only available in the smaller DB.

Of course, we can solve this by copying things back and forth, but we're
also thinking: why not just one big DB?

Anyone have any experiences with a similar project, and especially any
technical configurations that might be beneficial in using RDS?

Appreciate it.

-- 
Wells Oliver
wells.oliver@gmail.com <wellsoliver@gmail.com>

--000000000000c9009605cda2415d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi-- to keep it short, I feel like I&#39;ve generally hear=
d the larger your DB is, the less efficient it might run, likely due to dis=
k I/O. Maybe I&#39;m terribly mistaken in this perception.<div><br></div><d=
iv>We have two DBs, one primarily accessed by humans and systems, which is =
~1TB in size, and aggregates most of what we store in raw, longer format on=
 a second DB that is about ~6TB in size.</div><div><br></div><div>As we con=
sider plans to migrate to RDS, we&#39;ve talked a lot about combining=C2=A0=
the two as more and more the case is querying the larger DB and wanting dat=
a only available in the smaller DB.</div><div><br></div><div>Of course, we =
can solve this by copying things back and forth, but we&#39;re also thinkin=
g: why not just one big DB?</div><div><br></div><div>Anyone have any experi=
ences with a similar project, and especially any technical=C2=A0configurati=
ons that might be beneficial=C2=A0in using RDS?</div><div><br></div><div>Ap=
preciate it.<br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr" class=
=3D"gmail_signature" data-smartmail=3D"gmail_signature"><div dir=3D"ltr"><d=
iv>Wells Oliver<br><a href=3D"mailto:wellsoliver@gmail.com" target=3D"_blan=
k">wells.oliver@gmail.com</a></div></div></div></div></div>

--000000000000c9009605cda2415d--