2 replaced http://serverfault.com/ with https://serverfault.com/
source | link

Since you're on SSD you're better of disabling readahead. Seek time is not an issue for flash based drives. That's for the spinning era. It's more important to align the filesystem properly.

Postgresql is using 8k pages so best performance generally comes with matching blocksize.

With XFS use nobarrier and make the filesystem with proper agcount and logging. (http://serverfault.com/questions/222305/trying-to-determine-the-correct-number-of-xfs-allocation-groups-for-postgresql-shttps://serverfault.com/questions/222305/trying-to-determine-the-correct-number-of-xfs-allocation-groups-for-postgresql-s).

You can also benefit from having compressed file system like ZFS especially if your data cannot fit in cache and has to be read from disk. Usually I get 2-4x for databases which results in 2-4 times less blocks read from disk but that's very use case dependant. If you use ZFS use recordsize=8k, compression=lz4, primarycache=all and check if you need to set ashift for the particular disk (if it is using 512 byte or 4k blocks by running cat /sys/block/[device]/queue/physical_block_size). http://zfsonlinux.org/faq.html#PerformanceConsideration

Since you're on SSD you're better of disabling readahead. Seek time is not an issue for flash based drives. That's for the spinning era. It's more important to align the filesystem properly.

Postgresql is using 8k pages so best performance generally comes with matching blocksize.

With XFS use nobarrier and make the filesystem with proper agcount and logging. (http://serverfault.com/questions/222305/trying-to-determine-the-correct-number-of-xfs-allocation-groups-for-postgresql-s).

You can also benefit from having compressed file system like ZFS especially if your data cannot fit in cache and has to be read from disk. Usually I get 2-4x for databases which results in 2-4 times less blocks read from disk but that's very use case dependant. If you use ZFS use recordsize=8k, compression=lz4, primarycache=all and check if you need to set ashift for the particular disk (if it is using 512 byte or 4k blocks by running cat /sys/block/[device]/queue/physical_block_size). http://zfsonlinux.org/faq.html#PerformanceConsideration

Since you're on SSD you're better of disabling readahead. Seek time is not an issue for flash based drives. That's for the spinning era. It's more important to align the filesystem properly.

Postgresql is using 8k pages so best performance generally comes with matching blocksize.

With XFS use nobarrier and make the filesystem with proper agcount and logging. (https://serverfault.com/questions/222305/trying-to-determine-the-correct-number-of-xfs-allocation-groups-for-postgresql-s).

You can also benefit from having compressed file system like ZFS especially if your data cannot fit in cache and has to be read from disk. Usually I get 2-4x for databases which results in 2-4 times less blocks read from disk but that's very use case dependant. If you use ZFS use recordsize=8k, compression=lz4, primarycache=all and check if you need to set ashift for the particular disk (if it is using 512 byte or 4k blocks by running cat /sys/block/[device]/queue/physical_block_size). http://zfsonlinux.org/faq.html#PerformanceConsideration

1
source | link

Since you're on SSD you're better of disabling readahead. Seek time is not an issue for flash based drives. That's for the spinning era. It's more important to align the filesystem properly.

Postgresql is using 8k pages so best performance generally comes with matching blocksize.

With XFS use nobarrier and make the filesystem with proper agcount and logging. (http://serverfault.com/questions/222305/trying-to-determine-the-correct-number-of-xfs-allocation-groups-for-postgresql-s).

You can also benefit from having compressed file system like ZFS especially if your data cannot fit in cache and has to be read from disk. Usually I get 2-4x for databases which results in 2-4 times less blocks read from disk but that's very use case dependant. If you use ZFS use recordsize=8k, compression=lz4, primarycache=all and check if you need to set ashift for the particular disk (if it is using 512 byte or 4k blocks by running cat /sys/block/[device]/queue/physical_block_size). http://zfsonlinux.org/faq.html#PerformanceConsideration