| From: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com> |
|---|---|
| To: | Aissa BAMMOUNE IT <Aissa(dot)Bm(at)techno-dz(dot)com> |
| Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: TR: Re: Postgres and multiprocessor? |
| Date: | 2015-04-28 15:11:42 |
| Message-ID: | D94F5A78-2A37-445F-B542-84A7F77EF6AC@elevated-dev.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Apr 28, 2015, at 5:00 AM, Aissa BAMMOUNE IT <Aissa(dot)Bm(at)techno-dz(dot)com> wrote:
>
> J’ai un PostgreSQL installer dans un serveur dell Xeon® Processor E5-2407 (10M Cache, 2.20 GHz), PostgreSQLutilise un cœur de processeur pour ces analyses et sa prendre plus de temps, il y a une possibilité que le PostgreSQL utilise les 4 cœurs à la place d’un cœur (notion de multiprocesseur).
Also, have you checked to see whether your queries are CPU-bound or disk-bound? It’s really more common for disk to be the problem, and regardless there may be tuning that could be done. Try EXPLAIN ANALYZE on the worst queries, then post that here, along with the schema, and notes about db size, and tuning parameters from postgresql.conf.
--
Scott Ribe
scott_ribe(at)elevated-dev(dot)com
http://www.elevated-dev.com/
https://www.linkedin.com/in/scottribe/
(303) 722-0567 voice
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2015-04-28 15:13:05 | Re: TR: Re: Postgres and multiprocessor? |
| Previous Message | Scott Ribe | 2015-04-28 15:08:52 | Re: TR: Re: Postgres and multiprocessor? |