Timeline for Postgres 4x Slower Than It Was
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 15, 2020 at 9:05 | history | edited | CommunityBot |
Commonmark migration
|
|
| Aug 11, 2015 at 22:51 | comment | added | user1517922 | Thanks. I tried tuned, but it was hard to know what it was messing with, so I felt better changing the settings by hand. | |
| Aug 11, 2015 at 18:27 | comment | added | Kassandry | The problem with PgTune being this thorough is that it would need to include a lot of OS/Distro specific changes, as well as OS/Distro version changes alongside what suggestions it makes for PostgreSQL, which is outside its scope. Though, poking around more, I did find tuned for CentOS which should get you even farther along as well. Glad to be of help, and good luck! =) | |
| Aug 10, 2015 at 18:04 | vote | accept | user1517922 | ||
| Aug 10, 2015 at 15:55 | comment | added | user1517922 | Thanks! This is the type of information I was hoping for. There is so much to consider when running a large Postgres cluster! I wish PgTune or a similar tool was thorough enough to include these kinds of suggestions. Even just a tool to help you avoid the most common pitfalls / low hanging fruit would make a big difference. | |
| Aug 8, 2015 at 5:27 | comment | added | Kassandry |
Oh, I forgot as well. Set vm.swappiness=10, as recommended here
|
|
| Aug 8, 2015 at 5:25 | history | answered | Kassandry | CC BY-SA 3.0 |