| From: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
|---|---|
| To: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Linux VM Sizing |
| Date: | 2025-07-29 01:03:28 |
| Message-ID: | CANzqJaBjrVHymyrP6=O9dVxz6ihWssQc2xPWXBrz_DnHW6Nm_A@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Mon, Jul 28, 2025 at 7:42 PM Sam Stearns <sam(dot)stearns(at)dat(dot)com> wrote:
> Howdy,
>
> We are sizing a Linux VM to migrate our Oracle production database to. We
> are currently running on an Oracle Database Appliance. Oracle CPU / memory
> usage stats are:
>
> CPU % usage - 25% of 20 cores / 40 threads (Intel® Xeon® S4314 processor)
> Memory % usage - 100% usage of 600G SGA
>
Linux uses all available cache; is Oracle different? (IOW, would it also
use 100% of 800GB?)
> Based on the above can anyone give advice as to how to size the CPU /
> memory of the Linux VM, please?
>
Our 8TB Oracle DB was 6TB when migrated to PG 12 (this was a while ago)
and the AWS RDS Postgresql instance (which was spec'd -- before I got to
the project -- the same as the on-prem Linux server since the Oracle server
ran 60-70%) was constantly less 10% of capacity in CPU and RAM.
--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rui DeSousa | 2025-07-29 02:14:09 | Re: Linux VM Sizing |
| Previous Message | Rui DeSousa | 2025-07-29 00:47:40 | Re: Why many more deadlocks after upgrade to PG 17.5? |