Re: Toooo many context switches (maybe SLES8?)
От
Tom Lane
Тема
Re: Toooo many context switches (maybe SLES8?)
Дата
Msg-id
20498.1082057841@sss.pgh.pa.us
Ответ на
Re: Toooo many context switches (maybe SLES8?) (Joe Conway)
Список
Дерево обсуждения
Toooo many context switches (maybe SLES8?) Dirk Lutzebäck <lutzeb@aeccom.com>
Re: Toooo many context switches (maybe SLES8?) Joe Conway <mail@joeconway.com>
Re: Toooo many context switches (maybe SLES8?) Josh Berkus <josh@agliodbs.com>
Re: Toooo many context switches (maybe SLES8?) Dirk Lutzebäck <lutzeb@aeccom.com>
Re: Toooo many context switches (maybe SLES8?) Joe Conway <mail@joeconway.com>
Re: Toooo many context switches (maybe SLES8?) Tom Lane <tgl@sss.pgh.pa.us>
Re: Toooo many context switches (maybe SLES8?) Josh Berkus <josh@agliodbs.com>
Re: Toooo many context switches (maybe SLES8?) Dave Cramer <pg@fastcrypt.com>
Re: Toooo many context switches (maybe SLES8?) Dirk.Lutzebaeck@t-online.de (Dirk Lutzebaeck)
Re: Toooo many context switches (maybe SLES8?) Dave Cramer <pg@fastcrypt.com>
Joe Conway writes: >> Improve spinlock code for recent x86 processors: insert a PAUSE >> instruction in the s_lock() wait loop, and use test before test-and-set >> in TAS() macro to avoid unnecessary bus traffic. Patch from Manfred >> Spraul, reworked a bit by Tom. > I thought this had been committed to the 7.4 stable branch as well, but > it appears not. I am currently chasing what seems to be the same issue: massive context swapping on a dual Xeon system. I tried back-patching the above-mentioned patch ... it helps a little but by no means solves the problem ... regards, tom lane
В списке pgsql-performance по дате отправления