From: Ron Mayer <rm_pg@cheapcomplexdevices.com>
To: Magnus Hagander <magnus@hagander.net>
Cc: Jan Wieck <JanWieck@Yahoo.com>
Cc: Ron Mayer <rm_pg@cheapcomplexdevices.com>
Subject: Re: Priorities for users or queries?
Date: Fri, 16 Feb 2007 17:44:40 -0800
Message-ID: <45D65E08.7000306@cheapcomplexdevices.com> (raw)
In-Reply-To: <45CEE33B.8020303@hagander.net>
References: <000001c74da2$a9a4a990$6400a8c0@dualcore>
<45CEE33B.8020303@hagander.net>
Magnus Hagander wrote:
> Most likely, you do not want to do this. You *can* do it, but you are
> quite likely to suffer from priority inversion
Papers I've read suggest that the benefits of priorities
vastly outweigh the penalties of priority inversion for
virtually all workloads on most all RDBMs's including
PostgreSQL.
This CMU paper in particular tested PostgreSQL (and DB2)
on TPC-C and TPC-W workloads and found that indirectly
influencing I/O scheduling through CPU priorities
is a big win for postgresql.
http://www.cs.cmu.edu/~bianca/icde04.pdf
"For TPC-C running on PostgreSQL,
the simplest CPU scheduling policy (CPU-Prio) provides
a factor of 2 improvement for high-priority transactions,
while adding priority inheritance (CPU-Prio-Inherit)
provides a factor of 6 improvement while hardly
penalizing low-priority transactions."
Have you heard of any workload on any RDBMS where priority inversion
causes more harm than benefit?
Ron Mayer
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: rm_pg@cheapcomplexdevices.com, magnus@hagander.net, JanWieck@Yahoo.com
Subject: Re: Priorities for users or queries?
In-Reply-To: <45D65E08.7000306@cheapcomplexdevices.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