diff --git a/content/2015-11.md b/content/2015-11.md
index f4797c856..2831f646c 100644
--- a/content/2015-11.md
+++ b/content/2015-11.md
@@ -105,3 +105,26 @@ $ psql -c 'SELECT * from pg_stat_activity;' | grep cgspace | grep -c idle
 
 - At the time, the current DSpace pool size was 50...
 - I reduced the pool back to the default of 30, and reduced the `db.maxidle` settings from 10 to 8
+
+# 2015-11-29
+
+- Still more alerts that CGSpace has been up and down all day
+- Current database settings for DSpace:
+
+```
+db.maxconnections = 30
+db.maxwait = 5000
+db.maxidle = 8
+db.statementpool = true
+```
+
+- And idle connections:
+
+```
+$ psql -c 'SELECT * from pg_stat_activity;' | grep cgspace | grep -c idle
+49
+```
+
+- Perhaps I need to start drastically increasing the connection limits—like to 300—to see if DSpace's thirst can ever be quenched
+- On another note, SUNScholar's notes suggest adjusting some other postgres variables: http://wiki.lib.sun.ac.za/index.php/SUNScholar/Optimisations/Database
+- This might help with REST API speed (which I mentioned above and still need to do real tests)