Quote:
Originally Posted by FR-Nit
Could be that your CPU is the bottleneck. Did you try overclocking? Did the loading-time improve?
Well, when i first built the pc, I first overclocked the memory because that's what the postgresql guys told me was important. Then, because I was using a new prime95 version which isn't suited for haswell cpus, but I didn't know it at the time, I was getting absurdly high temperatures and stability issues I couldn't resolve. So I didn't pursue it.
I am not sure that the cpu is going to be a bottleneck just for the optane, but not for the relatively slower mainstream ssds. I should give it a try though at some point.
Quote:
optane seems to mostly only crush the competition in sequential reads at very low queue depths. optane does hold onto the lead in random reads until higher queue depths.
Funny how some things work out. I tried googling whether postgresql reads produce higher queue depths, but what I ended up finding instead was a postgresql tuner web app written by the guy who made it. Basically, you feed the page your specs and it gives you numbers to use on your postgresql config file.
After doing so and tinkering a bit more, I was actually able to shave another 18-26 seconds from loading times.
So basically, the big database loads in 1m 28s on the 900p and in 1m 35 s on the Samsung SSD while the small database loads in 44s in both disks.
I highly highly highly recommend to anyone interested in improving their database performance to use this pgtuner.
http://pgtune.leopard.in.ua/
PS. Also lower max_connections. I am experimenting now to find out what's the max connections the database uses, but it's way less than the default 100. And that's important, because the less max connections you have, the higher you can set your work mem.
PS2. But yeah, I don't think the 900p is going to work out.