On 12 December 2014 at 03:31, Simon Riggs wrote:
> Also attached is a new parameter called enable_sortedpath which can be
> used to turn on/off the sorted path generated by the planner.
Now with attachment. (Thanks Jeff!)
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQ
>
> - disk cache settings (EnDskCache - for SSD should be on or you're going
> to lose 90% of your performance)
>
Disk cache is enabled, I know there is a huge performance impact.
> - OS settings e.g.
>
> echo noop > /sys/block/sda/queue/scheduler
> echo 975 > /sys/block/sda/queue/nr_requests
>
> On 16 Dec 2014, at 14:51, Graeme B. Bell wrote:
>
>>
>> I don't understand the logic behind using drives,
>> which are best for random io, for sequent io workloads.
>
> Because they are also best for sequential IO. I get 1.3-1.4GB/second from 4
> SSDs in RAID or >500MB/s for single disk sy
>
> I don't understand the logic behind using drives,
> which are best for random io, for sequent io workloads.
Because they are also best for sequential IO. I get 1.3-1.4GB/second from 4
SSDs in RAID or >500MB/s for single disk systems, even with cheap models.
Are you getting more than that f
>
> I have a beast of a Dell server with the following specifications:
> • 4x Xeon E5-4657LV2 (48 cores total)
> • 196GB RAM
> • 2x SCSI 900GB in RAID1 (for the OS)
> • 8x Intel S3500 SSD 240GB in RAID10
> • H710p RAID controller, 1GB cache
> Centos 6.6, RAID10 SSDs u
