| From: | Francisco Olarte <folarte(at)peoplecall(dot)com> |
|---|---|
| To: | Rakesh Kumar <rakeshkumar464(at)outlook(dot)com> |
| Cc: | Melvin Davidson <melvin6925(at)gmail(dot)com>, David A <david(at)scalaacademy(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: My DB has has 5TB, many operations are very slow (on Google Cloud Compute) |
| Date: | 2016-10-11 19:16:29 |
| Message-ID: | CA+bJJbwtND0_jxfPgzcTVc0PtgykK++Q4JFBhXBhCa0MoOcLrg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Rakesh:
On Tue, Oct 11, 2016 at 9:00 PM, Rakesh Kumar
<rakeshkumar464(at)outlook(dot)com> wrote:
>>Cores do not help, postgres is single-threaded. RAM MAY help, but I
> I hope this is no longer true from 9.6 for those queries where PG can use parallelism.
It does, AFAIK, but for queries, not AFAIK for this kind of data
moving ops ( and I doubt it will, as presently you can easily saturate
the channels with a single core for that kind of simple ops, and
normally if you want to optimize this kind of op is better to target
concurrency ( table can be used while moving ) than pure speed .
Francisco Olarte.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jason Dusek | 2016-10-11 19:29:28 | SERIALIZABLE and INSERTs with multiple VALUES |
| Previous Message | Francisco Olarte | 2016-10-11 19:13:54 | Re: My DB has has 5TB, many operations are very slow (on Google Cloud Compute) |