Fwd: Process scheduling in postgres

From: raghu vineel <raghuvineel(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org, pgsql-novice(at)postgresql(dot)org
Subject: Fwd: Process scheduling in postgres
Date: 2016-04-22 08:30:45
Message-ID: CABRw-Q=Sh-qvSG4PVpVphv3cDQ4-d5OThYqO5P7r-2u8saFn=Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-novice

Hi,

I have a 4 core CPU for postgres and I have submitted 6 queries parallely
in 6 different sessions. But I am seeing only 1 query per CPU and the
remainig queries are queued. I am not sure why is it happening. Do you have
any special scheduler for postgres? I can see that CPU has been shared with
other non postgres processes but postgres processes are not sharing any CPU
within a core. The following is the process states.

*lms 2868 2209 98 07:20 ? 00:02:30 postgres: lms controller
[local] SELECTlms 2869 2209 98 07:20 ? 00:02:30 postgres: lms
controller [local] SELECT*
lms 2870 2209 0 07:20 ? 00:00:00 postgres: lms controller
[local] SELECT
lms 2871 2209 0 07:20 ? 00:00:00 postgres: lms controller
[local] SELECT
lms 2872 2209 0 07:20 ? 00:00:00 postgres: lms controller
[local] SELECT
*lms 2873 2209 98 07:20 ? 00:02:30 postgres: lms controller
[local] SELECT*

If you see above, three Select queries have been queued. They are acquiring
CPU only when there is a core without any postgres query running on it.

I know the postgres limitation of one query using only one core. But is
there any limitation of one CPU running only one query at a time?

Your help is appreciated.

Thanks and regards,
Vineel.

Responses

Browse pgsql-general by date

  From Date Subject
Next Message David Goodenough 2016-04-22 10:21:30 Re: Proper relational database?
Previous Message jje 2016-04-22 08:26:31 Re: Columnar store as default for PostgreSQL 10?

Browse pgsql-novice by date

  From Date Subject
Next Message Day, David 2016-04-22 12:06:19 Re: postgres connection issues
Previous Message neha khatri 2016-04-22 04:30:37 Re: pg_upgarde: The control data check for equal max_index_keys in old and new version