Re: Linux 2.6.24 Through Linux 2.6.33 Benchmarks

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Paolo Ornati
Date: Thursday, March 11, 2010 - 12:27 pm

On Wed, 10 Mar 2010 20:34:12 +0200
Anca Emanuel <anca.emanuel@gmail.com> wrote:


The extra performance was just a "bug":

http://www.mail-archive.com/pgsql-performance@postgresql.org/msg34841.html

"[This change] is required for safe behavior with volatile write caches
on drives. You could mount with -o nobarrier and [the performance drop]
would go away, but a sequence like write->fsync->lose power->reboot may
well find your file without the data that you synced, if the drive had
write caches enabled. If you know you have no write cache, or that it
is safely battery backed, then you can mount with -o nobarrier, and not
incur this penalty."

-- 
	Paolo Ornati
	Linux 2.6.33-00001-gbaac35c on x86_64
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Linux 2.6.24 Through Linux 2.6.33 Benchmarks, Anca Emanuel, (Wed Mar 10, 11:34 am)
Re: Linux 2.6.24 Through Linux 2.6.33 Benchmarks, Paolo Ornati, (Thu Mar 11, 12:27 pm)