| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20100311202712.58e4d444@gmail.com> Date: Thu, 11 Mar 2010 20:27:12 +0100 From: Paolo Ornati <ornati@...il.com> To: Anca Emanuel <anca.emanuel@...il.com> Cc: linux-kernel <linux-kernel@...r.kernel.org>, torvalds <torvalds@...ux-foundation.org> Subject: Re: Linux 2.6.24 Through Linux 2.6.33 Benchmarks On Wed, 10 Mar 2010 20:34:12 +0200 Anca Emanuel <anca.emanuel@...il.com> wrote: > In fact, the Linux 2.6.30 kernel > was 770% faster than its predecessor was and it remained that way with > the Linux 2.6.31 kernel and then regressed only slightly with the > Linux 2.6.32 kernel. With the new Linux 2.6.33 kernel, however, the > PostgreSQL performance atop the EXT3 file-system has fallen off a > cliff. 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists