From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | "drum(dot)lucas(at)gmail(dot)com" <drum(dot)lucas(at)gmail(dot)com> |
Cc: | Postgres General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: I/O - Increase RAM |
Date: | 2016-04-13 21:35:19 |
Message-ID: | 570EBB97.5030105@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 04/13/2016 01:59 PM, drum(dot)lucas(at)gmail(dot)com wrote:
>
>
> On 14 April 2016 at 08:52, Joshua D. Drake <jd(at)commandprompt(dot)com
> <mailto:jd(at)commandprompt(dot)com>> wrote:
>
> On 04/13/2016 01:43 PM, drum(dot)lucas(at)gmail(dot)com
> <mailto:drum(dot)lucas(at)gmail(dot)com> wrote:
>
> Question:
>
> I know that might not be the best option, but by increasing the
> RAM and
> the CACHE would help, right?
>
>
> might, not necessarily would.
>
>
> Would be nice if you could explain why not / why yes
For reads the more things in cache the more performance.
For writes the topic is more complicated but the long and short is this:
The moment you flush your cache (evict a bunch of buffers, linux dumping
out its cache etc..) you are going to get hammered.
JD
--
Command Prompt, Inc. http://the.postgres.company/
+1-503-667-4564
PostgreSQL Centered full stack support, consulting and development.
Everyone appreciates your honesty, until you are honest with them.
From | Date | Subject | |
---|---|---|---|
Next Message | Mike Sofen | 2016-04-13 21:39:51 | Re: I/O - Increase RAM |
Previous Message | drum.lucas@gmail.com | 2016-04-13 20:59:16 | Re: I/O - Increase RAM |