From: | Greg Smith <gsmith(at)gregsmith(dot)com> |
---|---|
To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Sorted writes in checkpoint |
Date: | 2007-06-15 04:53:41 |
Message-ID: | Pine.GSO.4.64.0706150040280.2986@westnet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
On Thu, 14 Jun 2007, Gregory Maxwell wrote:
> Linux has some instrumentation that might be useful for this testing,
> echo 1 > /proc/sys/vm/block_dump
That bit was developed for tracking down who was spinning the hard drive
up out of power saving mode, and I was under the impression that very
rough feature isn't useful at all here. I just tried to track down again
where I got that impression from, and I think it was this thread:
http://linux.slashdot.org/comments.pl?sid=231817&cid=18832379
This mentions general issues figuring out who was responsible for a write
and specifically mentions how you'll have to reconcile two different paths
if fsync is mixed in. Not saying it won't work, it's just obvious using
the block_dump output isn't a simple job.
(For anyone who would like an intro to this feature, try
http://www.linuxjournal.com/node/7539/print and
http://toadstool.se/journal/2006/05/27/monitoring-filesystem-activity-under-linux-with-block_dump
)
--
* Greg Smith gsmith(at)gregsmith(dot)com http://www.gregsmith.com Baltimore, MD
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2007-06-15 07:19:40 | Re: Load Distributed Checkpoints test results |
Previous Message | Oleg Bartunov | 2007-06-15 04:46:35 | Re: tsearch_core patch: permissions and security issues |
From | Date | Subject | |
---|---|---|---|
Next Message | Zeugswetter Andreas ADI SD | 2007-06-15 09:14:20 | Re: Sorted writes in checkpoint |
Previous Message | Gregory Maxwell | 2007-06-15 02:37:14 | Re: Sorted writes in checkpoint |