pg.ddx.io pgsql-performance@postgresql.org mailing list archive
help / color / mirror / Atom feedPostgreSQL VACCUM killing CPU
5+ messages / 4 participants
[nested] [flat]
* PostgreSQL VACCUM killing CPU
@ 2006-05-09 10:19 blender@jaskom.pl
2006-05-10 03:03 ` Re: PostgreSQL VACCUM killing CPU Will Reese <wreese@rackspace.com>
2006-05-10 14:17 ` Re: PostgreSQL VACCUM killing CPU Wu Fengguang <wfg@mail.ustc.edu.cn>
0 siblings, 2 replies; 5+ messages in thread
From: blender@jaskom.pl @ 2006-05-09 10:19 UTC (permalink / raw)
To: pgsql-performance
Hi all !
I have got such problem.
Im running Postgresql 7.3.2 on Linux 2.6.13.
What is see when VACCUM is running and killing my CPU is:
Cpu(s): 3.2% us, 0.0% sy, 0.0% ni, 0.0% id, 96.8% wa, 0.0% hi,
0.0% si
what i am worry about is "96.8% wa" why is it like that?
what is the process waiting for ?
could somone explain me that please? :)
Best regards
david
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: PostgreSQL VACCUM killing CPU
2006-05-09 10:19 PostgreSQL VACCUM killing CPU blender@jaskom.pl
@ 2006-05-10 03:03 ` Will Reese <wreese@rackspace.com>
2006-05-10 03:24 ` Re: PostgreSQL VACCUM killing CPU Michael Glaesemann <grzm@seespotcode.net>
2006-05-10 03:28 ` Re: PostgreSQL VACCUM killing CPU Michael Glaesemann <grzm@seespotcode.net>
1 sibling, 2 replies; 5+ messages in thread
From: Will Reese @ 2006-05-10 03:03 UTC (permalink / raw)
To: pgsql-performance
The "wa" means waiting on IO. Vacuum is a very IO intensive
process. You can use tools like vmstat and iostat to see how much
disk IO is occurring. Also, sar is very helpful for trending these
values over time.
-- Will Reese http://blog.rezra.com
On May 9, 2006, at 5:19 AM, blender@jaskom.pl wrote:
> Hi all !
>
> I have got such problem.
> Im running Postgresql 7.3.2 on Linux 2.6.13.
> What is see when VACCUM is running and killing my CPU is:
>
> Cpu(s): 3.2% us, 0.0% sy, 0.0% ni, 0.0% id, 96.8% wa, 0.0% hi,
> 0.0% si
>
> what i am worry about is "96.8% wa" why is it like that?
>
> what is the process waiting for ?
>
> could somone explain me that please? :)
>
> Best regards
> david
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: PostgreSQL VACCUM killing CPU
2006-05-09 10:19 PostgreSQL VACCUM killing CPU blender@jaskom.pl
2006-05-10 03:03 ` Re: PostgreSQL VACCUM killing CPU Will Reese <wreese@rackspace.com>
@ 2006-05-10 03:24 ` Michael Glaesemann <grzm@seespotcode.net>
1 sibling, 0 replies; 5+ messages in thread
From: Michael Glaesemann @ 2006-05-10 03:24 UTC (permalink / raw)
To: Will Reese <wreese@rackspace.com>; +Cc: pgsql-performance
>> I have got such problem.
>> Im running Postgresql 7.3.2 on Linux 2.6.13.
Also, you should seriously consider upgrading. 8.1.3 is the current
PostgreSQL release. If you must remain on 7.3, at least upgrade to
7.3.14, which contains many bugfixes.
Michael Glaesemann
grzm seespotcode net
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: PostgreSQL VACCUM killing CPU
2006-05-09 10:19 PostgreSQL VACCUM killing CPU blender@jaskom.pl
2006-05-10 03:03 ` Re: PostgreSQL VACCUM killing CPU Will Reese <wreese@rackspace.com>
@ 2006-05-10 03:28 ` Michael Glaesemann <grzm@seespotcode.net>
1 sibling, 0 replies; 5+ messages in thread
From: Michael Glaesemann @ 2006-05-10 03:28 UTC (permalink / raw)
To: blender@jaskom.pl; +Cc: pgsql-performance
>> I have got such problem.
>> Im running Postgresql 7.3.2 on Linux 2.6.13.
Also, you should seriously consider upgrading. 8.1.3 is the current
PostgreSQL release. If you must remain on 7.3, at least upgrade to
7.3.14, which contains *many* bugfixes.
Michael Glaesemann
grzm seespotcode net
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: PostgreSQL VACCUM killing CPU
2006-05-09 10:19 PostgreSQL VACCUM killing CPU blender@jaskom.pl
@ 2006-05-10 14:17 ` Wu Fengguang <wfg@mail.ustc.edu.cn>
1 sibling, 0 replies; 5+ messages in thread
From: Wu Fengguang @ 2006-05-10 14:17 UTC (permalink / raw)
To: blender@jaskom.pl; +Cc: pgsql-performance
On Tue, May 09, 2006 at 03:19:08AM -0700, blender@jaskom.pl wrote:
> I have got such problem.
> Im running Postgresql 7.3.2 on Linux 2.6.13.
> What is see when VACCUM is running and killing my CPU is:
>
> Cpu(s): 3.2% us, 0.0% sy, 0.0% ni, 0.0% id, 96.8% wa, 0.0% hi,
> 0.0% si
>
> what i am worry about is "96.8% wa" why is it like that?
It's killing your disk drives instead of CPU(which is mostly _idle_
waiting for I/O completion).
Run this command to get an idea of the I/O activities:
iostat -x 3 3
[AD]Running a kernel patched with adaptive read-ahead may help it:
http://www.vanheusden.com/ara/adaptive-readahead-11.1-2.6.16.5.patch.gz
^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~2006-05-10 14:17 UTC | newest]
Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2006-05-09 10:19 PostgreSQL VACCUM killing CPU blender@jaskom.pl
2006-05-10 03:03 ` Will Reese <wreese@rackspace.com>
2006-05-10 03:24 ` Michael Glaesemann <grzm@seespotcode.net>
2006-05-10 03:28 ` Michael Glaesemann <grzm@seespotcode.net>
2006-05-10 14:17 ` Wu Fengguang <wfg@mail.ustc.edu.cn>
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