On Mon, Apr 24, 2017 at 12:43 PM, pinker <pin...@onet.eu> wrote: > 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. >
All good options. Also make sure zone reclaim mode is set to 0 on big memory machines. It's a great setting for big VM hosts but a terrible one for file or db servers. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
