pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Benjamin Arai <benjamin@araisoft.com>
To: Ron Mayer <rm_pg@cheapcomplexdevices.com>
Cc: Bruce Momjian <bruce@momjian.us>
Cc: pgsql-general@postgresql.org
Subject: Re: Priorities for users or queries?
Date: Fri, 23 Feb 2007 12:49:30 -0800
Message-ID: <45DF535A.6090008@araisoft.com> (raw)
In-Reply-To: <45DB81EA.9080401@cheapcomplexdevices.com>
References: <45D65E08.7000306@cheapcomplexdevices.com>
	<200702170152.l1H1qax16645@momjian.us>
	<45DB81EA.9080401@cheapcomplexdevices.com>

My problem with [1] is that even for 10 users the percentage of time
spent in locks is very high.  Can priorities scale?

Benjamin

Ron Mayer wrote:
> Bruce Momjian wrote:
>   
>> Hard to argue with that.
>>     
>
> Is it a strong enough argument to add a TODO?
>
>
> I'm thinking some sort of TODO might be called for.
>
> Perhaps two TODOs?
>   * Use the OS's priority features to prioritize
>     backends (and document that it might work
>     better with OS's that support priority inheritance).
>   * Investigate if postgresql could develop an
>     additional priority mechanism instead of using
>     the OS's.
>
>   
>> Ron Mayer wrote:
>>     
>>> Magnus Hagander wrote: ...
>>>       
>>>> quite likely to suffer from priority inversion
>>>>         
>>> ... CMU paper... tested PostgreSQL (and DB2) on TPC-C 
>>> and TPC-W ...found that...I/O scheduling through 
>>> CPU priorities is a big win for postgresql.
>>>
>>> http://www.cs.cmu.edu/~bianca/icde04.pdf
>>>       
>
> Setting priorities seems a rather common request,
> supposedly coming up every couple months [5].
>
> The paper referenced [1] suggests that even with
> naive schedulers, use of CPU priorities is very
> effective for CPU and I/O intensive PostgreSQL
> workloads.
>
> If someone eventually finds a workload that does suffer
> worse performance due to priority inversion,
> (a) they could switch to an OS and scheduler
> that supports priority inheritance;
> (b) it'd be an interesting case for a paper
> rebutting the CMU one; and
> (c) they don't have to use priorities.
>
> If a user does find he wants priority inheritance it
> seems Linux[1], BSD[2], some flavors of Windows[3],
> and Solaris[4] all seem to be options; even though
> I've only seen PostgreSQL specifically tested for
> priority inversion problems with Linux (which did
> not find problems but found additional benefit of
> using priority inheritance).
>
>
>
>
> [1] Linux with Priority inheritance showing benefits for
>     PostgreSQL
>     http://www.cs.cmu.edu/~bianca/icde04.pdf
> [2] BSD priority inheritance work mentioned:
>     http://www.freebsd.org/news/status/report-july-2004-dec-2004.html
> [3] Windows priority inheritance stuff:
>     http://msdn2.microsoft.com/en-us/library/aa915356.aspx
> [4] Solaris priority inheritance stuff
>     http://safari5.bvdep.com/0131482092/ch17lev1sec7
>     http://www.itworld.com/AppDev/1170/swol-1218-insidesolaris/
> [5] Tom suggests that priorities are a often requested feature.
>     http://svr5.postgresql.org/pgsql-performance/2006-05/msg00463.php
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
>
>                http://www.postgresql.org/docs/faq
>
>   




view thread (30+ messages)  latest in thread

Message-ID: <45DF535A.6090008@araisoft.com>
Permalink:  ../45DF535A.6090008@araisoft.com/
Also on:    postgresql.org/message-id/45DF535A.6090008@araisoft.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: benjamin@araisoft.com, rm_pg@cheapcomplexdevices.com, bruce@momjian.us, pgsql-general@postgresql.org
  Subject: Re: Priorities for users or queries?
  In-Reply-To: <45DF535A.6090008@araisoft.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox