pg.ddx.io pgsql-performance@postgresql.org mailing list archive
help / color / mirror / Atom feedRESOLVED: Re: Wierd context-switching issue on Xeon
4+ messages / 3 participants
[nested] [flat]
* RESOLVED: Re: Wierd context-switching issue on Xeon
@ 2004-04-16 13:03 Dirk Lutzebäck <lutzeb@aeccom.com>
0 siblings, 2 replies; 4+ messages in thread
From: Dirk Lutzebäck @ 2004-04-16 13:03 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; josh@agliodbs.com; pgsql-performance; +Cc: Sven Geisler <sgeisler@aeccom.com>
Tom, Josh,
I think we have the problem resolved after I found the following note
from Tom:
> A large number of semops may mean that you have excessive contention
on some lockable
> resource, but I don't have enough info to guess what resource.
This was the key to look at: we were missing all indices on table which
is used heavily and does lots of locking. After recreating the missing
indices the production system performed normal. No, more excessive
semop() calls, load way below 1.0, CS over 20.000 very rare, more in
thousands realm and less.
This is quite a relief but I am sorry that the problem was so stupid and
you wasted some time although Tom said he had also seem excessive
semop() calls on another Dual XEON system.
Hyperthreading was turned off so far but will be turned on again the
next days. I don't expect any problems then.
I'm not sure if this semop() problem is still an issue but the database
behaves a bit out of bounds in this situation, i.e. consuming system
resources with semop() calls 95% while tables are locked very often and
longer.
Thanks for your help,
Dirk
At last here is the current vmstat 1 excerpt where the problem has been
resolved:
procs -----------memory---------- ---swap-- -----io---- --system--
----cpu----
r b swpd free buff cache si so bi bo in cs us sy
id wa
1 0 2308 232508 201924 6976532 0 0 136 464 628 812 5
1 94 0
0 0 2308 232500 201928 6976628 0 0 96 296 495 484 4
0 95 0
0 1 2308 232492 201928 6976628 0 0 0 176 347 278 1
0 99 0
0 0 2308 233484 201928 6976596 0 0 40 580 443 351 8
2 90 0
1 0 2308 233484 201928 6976696 0 0 76 692 792 651 9
2 88 0
0 0 2308 233484 201928 6976696 0 0 0 20 132 34 0
0 100 0
0 0 2308 233484 201928 6976696 0 0 0 76 177 90 0
0 100 0
0 1 2308 233484 201928 6976696 0 0 0 216 321 250 4
0 96 0
0 0 2308 233484 201928 6976696 0 0 0 116 417 240 8
0 92 0
0 0 2308 233484 201928 6976784 0 0 48 600 403 270 8
0 92 0
0 0 2308 233464 201928 6976860 0 0 76 452 1064 2611 14
1 84 0
0 0 2308 233460 201932 6976900 0 0 32 256 587 587 12
1 87 0
0 0 2308 233460 201932 6976932 0 0 32 188 379 287 5
0 94 0
0 0 2308 233460 201932 6976932 0 0 0 0 103 8 0
0 100 0
0 0 2308 233460 201932 6976932 0 0 0 0 102 14 0
0 100 0
0 1 2308 233444 201948 6976932 0 0 0 348 300 180 1
0 99 0
1 0 2308 233424 201948 6976948 0 0 16 380 739 906 4
2 93 0
0 0 2308 233424 201948 6977032 0 0 68 260 724 987 7
0 92 0
0 0 2308 231924 201948 6977128 0 0 96 344 1130 753 11
1 88 0
1 0 2308 231924 201948 6977248 0 0 112 324 687 628 3
0 97 0
0 0 2308 231924 201948 6977248 0 0 0 192 575 430 5
0 95 0
1 0 2308 231924 201948 6977248 0 0 0 264 208 124 0
0 100 0
0 0 2308 231924 201948 6977264 0 0 16 272 380 230 3
2 95 0
0 0 2308 231924 201948 6977264 0 0 0 0 104 8 0
0 100 0
0 0 2308 231924 201948 6977264 0 0 0 48 258 92 1
0 99 0
0 0 2308 231816 201948 6977484 0 0 212 268 456 384 2
0 98 0
0 0 2308 231816 201948 6977484 0 0 0 88 453 770 0
0 99 0
0 0 2308 231452 201948 6977680 0 0 196 476 615 676 5
0 94 0
0 0 2308 231452 201948 6977680 0 0 0 228 431 400 2
0 98 0
0 0 2308 231452 201948 6977680 0 0 0 0 237 58 3
0 97 0
0 0 2308 231448 201952 6977680 0 0 0 0 365 84 2
0 97 0
0 0 2308 231448 201952 6977680 0 0 0 40 246 108 1
0 99 0
0 0 2308 231448 201952 6977776 0 0 96 352 606 1026 4
2 94 0
0 0 2308 231448 201952 6977776 0 0 0 240 295 266 5
0 95 0
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: RESOLVED: Re: Wierd context-switching issue on Xeon
@ 2004-04-16 13:49 Tom Lane <tgl@sss.pgh.pa.us>
parent: Dirk Lutzebäck <lutzeb@aeccom.com>
1 sibling, 0 replies; 4+ messages in thread
From: Tom Lane @ 2004-04-16 13:49 UTC (permalink / raw)
To: Dirk Lutzebäck <lutzeb@aeccom.com>; +Cc: josh@agliodbs.com, pgsql-performance@postgresql.org, Sven Geisler <sgeisler@aeccom.com>
=?ISO-8859-1?Q?Dirk_Lutzeb=E4ck?= <lutzeb@aeccom.com> writes:
> This was the key to look at: we were missing all indices on table which
> is used heavily and does lots of locking. After recreating the missing
> indices the production system performed normal. No, more excessive
> semop() calls, load way below 1.0, CS over 20.000 very rare, more in
> thousands realm and less.
Hmm ... that's darn interesting. AFAICT the test case I am looking at
for Josh's client has no such SQL-level problem ... but I will go back
and double check ...
regards, tom lane
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: RESOLVED: Re: Wierd context-switching issue on Xeon
@ 2004-04-16 16:58 Josh Berkus <josh@agliodbs.com>
parent: Dirk Lutzebäck <lutzeb@aeccom.com>
1 sibling, 1 reply; 4+ messages in thread
From: Josh Berkus @ 2004-04-16 16:58 UTC (permalink / raw)
To: Dirk Lutzebäck <lutzeb@aeccom.com>; Tom Lane <tgl@sss.pgh.pa.us>; pgsql-performance; +Cc: Sven Geisler <sgeisler@aeccom.com>
Dirk,
> I'm not sure if this semop() problem is still an issue but the database
> behaves a bit out of bounds in this situation, i.e. consuming system
> resources with semop() calls 95% while tables are locked very often and
> longer.
It would be helpful to us if you could test this with the indexes disabled on
the non-Bigmem system. I'd like to eliminate Bigmem as a factor, if
possible.
--
-Josh Berkus
______AGLIO DATABASE SOLUTIONS___________________________
Josh Berkus
Enterprise vertical business josh@agliodbs.com
and data analysis solutions (415) 752-2387
and database optimization fax 651-9224
utilizing Open Source technology San Francisco
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: RESOLVED: Re: Wierd context-switching issue on Xeon
@ 2004-04-19 07:27 Dirk Lutzebäck <lutzeb@aeccom.com>
parent: Josh Berkus <josh@agliodbs.com>
0 siblings, 0 replies; 4+ messages in thread
From: Dirk Lutzebäck @ 2004-04-19 07:27 UTC (permalink / raw)
To: josh@agliodbs.com; +Cc: Tom Lane <tgl@sss.pgh.pa.us>; pgsql-performance
Josh, I cannot reproduce the excessive semop() on a Dual XEON DP on a
non-bigmem kernel, HT on. Interesting to know if the problem is related
to XEON MP (as Tom wrote) or bigmem.
Josh Berkus wrote:
>Dirk,
>
>
>
>>I'm not sure if this semop() problem is still an issue but the database
>>behaves a bit out of bounds in this situation, i.e. consuming system
>>resources with semop() calls 95% while tables are locked very often and
>>longer.
>>
>>
>
>It would be helpful to us if you could test this with the indexes disabled on
>the non-Bigmem system. I'd like to eliminate Bigmem as a factor, if
>possible.
>
>
>
^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2004-04-19 07:27 UTC | newest]
Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2004-04-16 13:03 RESOLVED: Re: Wierd context-switching issue on Xeon Dirk Lutzebäck <lutzeb@aeccom.com>
2004-04-16 13:49 ` Tom Lane <tgl@sss.pgh.pa.us>
2004-04-16 16:58 ` Josh Berkus <josh@agliodbs.com>
2004-04-19 07:27 ` Dirk Lutzebäck <lutzeb@aeccom.com>
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