Timeline for answer to Optimise PostgreSQL for fast testing by mys
Current License: CC BY-SA 3.0
Post Revisions
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 2, 2017 at 0:38 | comment | added | Craig Ringer | @A-B-B Yes, but you've also got OS buffer caching effects at work. All those params are a bit hand-wavey anyway... | |
| Feb 5, 2015 at 21:16 | comment | added | Asclepius | The value of 1.1 for SSD seems very unqualified. I acknowledge that it's what some professionals have blindly recommended. Even SSDs are significantly faster for sequential reads than random reads. | |
| Feb 5, 2015 at 17:30 | history | edited | Asclepius | CC BY-SA 3.0 |
Removed an unnecessary ending statement.
|
| Feb 23, 2012 at 17:37 | comment | added | intgr |
Note that if you're already running with fsync=off, putting pg_xlog on a separate disk doesn't improve much anymore.
|
|
| Feb 23, 2012 at 6:05 | history | answered | mys | CC BY-SA 3.0 |