Dear Shaun, Thanks for that - it's really interesting to know. On 02/01/13 21:46, Shaun Thomas wrote:
Hey everyone! After much testing and hair-pulling, we've confirmed two kernel settings that should always be modified in production Linux systems. Especially new ones with the completely fair scheduler (CFS) as opposed to the O(1) scheduler.
Does it apply to all types of production system, or just to certain workloads?
For example, what happens when there are only one or two concurrent processes? (i.e. there are always several more CPU cores than there are actual connections).
* sched_autogroup_enabled This is a relatively new patch which Linus lauded back in late 2010. It basically groups tasks by TTY so perceived responsiveness is improved. But on server systems, large daemons like PostgreSQL are going to be launched from the same pseudo-TTY, and be effectively choked out of CPU cycles in favor of less important tasks.
I've got several production servers using Postgres: I'd like to squeeze a bit more performance out of them, but in all cases, one (sometimes two) CPU cores are (sometimes) maxed out, but there are always several cores permanently idling. So does this apply here?
Thanks for your advice, Richard -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
