I've seen very big differences with huge_pages set to on, especially in context of CPU usage on multiple socket servers. You could play as well with storage options, for instance inode size and check if there is any advantage for your db from inlining, which is supported by xfs. You can find more informations here: http://beegfs.com/wiki/StorageServerTuning An interesting option for WAL would be to add the mount option- allocsize - and set it to 16MB - so the exact size of WAL segment to reduce the risk of fragmentation and optimal streaming write throughput. -- View this message in context: http://www.postgresql-archive.org/Block-size-recommendation-for-Red-Hat-Linux-7-2-tp5958026p5958066.html Sent from the PostgreSQL - general mailing list archive at Nabble.com. -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
