N****w
发帖数: 21578 | 1 http://www.phoronix.com/scan.php?page=article&item=linux_perf_regressions&num=2
PostgreSQL 只有以前 20% 的性能
看来 ext3 就没这事
When asked about the commit, Red Hat's Eric Sandeen shared:
"Hey, thanks for doing the digging :)
It is required for safe behavior with volatile write caches on drives.
You could mount with -o nobarrier and it 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 enabl | y***d
发帖数: 2330 | 2 似乎不无道理，还是 SSD 吧
backed
【在 N****w 的大作中提到】
: http://www.phoronix.com/scan.php?page=article&item=linux_perf_regressions&num=2
: PostgreSQL 只有以前 20% 的性能
: 看来 ext3 就没这事
: When asked about the commit, Red Hat's Eric Sandeen shared:
: "Hey, thanks for doing the digging :)
: It is required for safe behavior with volatile write caches on drives.
: You could mount with -o nobarrier and it 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 enabl
| m******t
发帖数: 2416 | 3 It's Ted Tso admitting that one could be right
in theory but wrong in reality.
page=article&item=linux_perf_regressions&num=2
drives.
sequence
the
backed
【在 N****w 的大作中提到】
: http://www.phoronix.com/scan.php?page=article&item=linux_perf_regressions&num=2
: PostgreSQL 只有以前 20% 的性能
: 看来 ext3 就没这事
: When asked about the commit, Red Hat's Eric Sandeen shared:
: "Hey, thanks for doing the digging :)
: It is required for safe behavior with volatile write caches on drives.
: You could mount with -o nobarrier and it 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 enabl
|
|
