Re: [PERFORM] can't explain commit performance win7 vs linux : 8000/s vs 419/s

my guess: - maybe the NTFS compression is enabled? [ "Compress this drive to save disk space” ? ] [ your test data is ideal for compression: VALUES ('AA.. 250 times') ] - or Windows Samsung Magician extreme settings? or RAPID mode cache enabled? "RAPID mode is a RAM caching feature.

Re: [PERFORM] can't explain commit performance win7 vs linux : 8000/s vs 419/s

On Sat, Jun 25, 2016 at 9:19 AM, t.dalpo...@gmail.com wrote: > Hi, > I've postgres 9.5.3 installed on win7 64 bit, and ubuntu 16.04tls 64 bit, > same SSD (evo 850 pro) , two different partitions. Laptop is 3.8Ghz. > I've in each partition a simple database with one table called data256 with > one

Re: [PERFORM] can't explain commit performance win7 vs linux : 8000/s vs 419/s

"t.dalpo...@gmail.com" writes: > Performance: > Win7: 8000 write/sec > Linux: 419 write/sec My immediate reaction to that is that Windows isn't actually writing the data to disk when it should in order to guarantee that commits are persistent. There are multiple layers that might be trying to op

[PERFORM] can't explain commit performance win7 vs linux : 8000/s vs 419/s

Hi, I've postgres 9.5.3 installed on win7 64 bit, and ubuntu 16.04tls 64 bit, same SSD (evo 850 pro) , two different partitions. Laptop is 3.8Ghz. I've in each partition a simple database with one table called data256 with one column of 256 char. I wrote a program using libpq which: 1 connects