| Time |
Nick |
Message |
| 07:00 |
|
collum joined #evergreen |
| 08:36 |
|
Dyrcona joined #evergreen |
| 10:20 |
|
Christineb joined #evergreen |
| 10:27 |
|
Dyrcona joined #evergreen |
| 10:50 |
Dyrcona |
Following up on my memory comments from last week, memory management seems to have improved on the test/dev system since changing vm.overcommit_memory to 0 to let the kernel heuristics figure it out. This is on a system running PostgreSQL and Evergreen all on 1 machine. |
| 11:47 |
|
jihpringle joined #evergreen |
| 11:56 |
|
beardicus joined #evergreen |
| 13:51 |
Bmagic |
Good to know! |
| 14:45 |
csharp_ |
vm.overcommit_memory = 0 |
| 14:46 |
csharp_ |
^^ on PINES primary DB |
| 14:50 |
Dyrcona |
csharp_: We're using vm.overcommit_memory = 2 on our db server. On a mixed use server, that doesn't seem to work out so well, and neither did 1. |
| 15:05 |
csharp_ |
hmm |
| 15:19 |
Dyrcona |
If it's working for you, don't change it. :) |
| 15:41 |
|
Rogan joined #evergreen |
| 16:49 |
Bmagic |
Has anyone noticed that after the security patches, you can't sort by columns in the AngularJS patron search results? |
| 17:30 |
jmurray-isl |
Didn't Bill put out a fix for that? |
| 17:32 |
jmurray-isl |
2153879 |
| 18:07 |
jeff |
yes, that sounds like bug 2153879: https://bugs.launchpad.net/evergreen/+bug/2153879 |
