| From: | Greg Smith <greg(at)2ndquadrant(dot)com> |
|---|---|
| To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Spread checkpoint sync |
| Date: | 2011-01-17 18:48:54 |
| Message-ID: | 4D348F16.5070102@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Jeff Janes wrote:
> Have you ever tested Robert's other idea of having a metronome process
> do a periodic fsync on a dummy file which is located on the same ext3fs
> as the table files? I think that that would be interesting to see.
>
To be frank, I really don't care about fixing this behavior on ext3,
especially in the context of that sort of hack. That filesystem is not
the future, it's not possible to ever really make it work right, and
every minute spent on pandering to its limitations would be better spent
elsewhere IMHO. I'm starting with the ext3 benchmarks just to provide
some proper context for the worst-case behavior people can see right
now, and to make sure refactoring here doesn't make things worse on it.
My target is same or slightly better on ext3, much better on XFS and ext4.
--
Greg Smith 2ndQuadrant US greg(at)2ndQuadrant(dot)com Baltimore, MD
PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.us
"PostgreSQL 9.0 High Performance": http://www.2ndQuadrant.com/books
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-01-17 18:57:13 | Re: Replication logging |
| Previous Message | Chris Browne | 2011-01-17 18:43:26 | Review: compact fsync request queue on overflow |