官术网_书友最值得收藏!

Summary

There aren't a lot of easy answers for what filesystem to use or how to arrange your disks. It's better to err on the side of paranoia, not performance, if you expect to keep your database intact under the sort of odd things that will happen to it in production. And unfortunately, maximum reliability is usually slower too. The most valuable thing you can do is be systematic in how you test. Instrument what you're doing, benchmark whenever possible, and always try to collect reproducible examples of realistic workloads whenever they appear.

  • Filesystem crash protection is mostly commonly done by journaling writes, which adds overhead but makes recovery time after unclean shutdown predictable.
  • On Linux, the ext3 filesystem allows a wide variety of tuning possibilities for its journal. While not the best performer, its occasional problem spots are at least well understood. Both XFS and ext4 are at early production quality right now, and expected to become increasingly viable alternatives to ext3 in the near future.
  • Solaris and FreeBSD both have older UFS filesystems and the newer ZFS available. ZFS has several features that make it uniquely suited for large database installations.
  • The NTFS filesystem on Windows shares many fundamentals with the UNIX-based ones popular on other operating systems.
  • Increasing read-ahead, stopping updates to file access timestamps, and adjusting the amount of memory used for caching are common tuning techniques needed to get good performance on most operating systems.
  • PostgreSQL allows relocating parts of the database through both symbolic links and creation of tablespaces.
  • The optimal way to arrange the components of a database across many available disks is very dependent on the specific application and usage pattern.
主站蜘蛛池模板: 德兴市| 桐柏县| 烟台市| 泰兴市| 秦皇岛市| 大足县| 新竹县| 石狮市| 南部县| 香港 | 巴南区| 方山县| 淅川县| 红安县| 晴隆县| 扎鲁特旗| 余江县| 惠东县| 靖江市| 遂昌县| 六枝特区| 兴城市| 体育| 洛隆县| 黎平县| 南召县| 宕昌县| 海南省| 洪江市| 崇文区| 格尔木市| 马公市| 卢龙县| 安多县| 德庆县| 永兴县| 皮山县| 隆德县| 敦化市| 保亭| 绥阳县|