diff --git a/content/post/2017-02.md b/content/post/2017-02.md
index 2267c529e..3294745d3 100644
--- a/content/post/2017-02.md
+++ b/content/post/2017-02.md
@@ -70,4 +70,17 @@ $ ./fix-metadata-values.py -i ccafs-flagships-feb7.csv -f cg.subject.ccafs -t co
## 2017-02-15
-- Update rvm on DSpace Test and CGSpace as there was a [security disclosure about versions <= 1.28.0](https://github.com/justinsteven/advisories/blob/master/2017_rvm_cd_command_execution.md)
+- Update rvm on DSpace Test and CGSpace as there was a [security disclosure about versions less than 1.28.0](https://github.com/justinsteven/advisories/blob/master/2017_rvm_cd_command_execution.md)
+
+## 2017-02-16
+
+- Looking at memory info from munin on CGSpace:
+
+![CGSpace meminfo](/cgspace-notes/2017/02/meminfo_phisical-week.png)
+
+- We are using only ~8GB of RAM for applications, and 16GB for caches!
+- The Linode machine we're on has 24GB of RAM but only because that's the only instance that had enough disk space for us (384GB)...
+- We should probably look into Google Compute Engine or Digital Ocean where we can get more storage without having to follow a linear increase in instance pricing for CPU/memory as well
+- Especially because we only use 2 out of 8 CPUs basically:
+
+![CGSpace CPU](/cgspace-notes/2017/02/cpu-week.png)
diff --git a/public/2017-02/index.html b/public/2017-02/index.html
index aa93865b3..afb06faac 100644
--- a/public/2017-02/index.html
+++ b/public/2017-02/index.html
@@ -92,7 +92,7 @@ Looks like we’ll be using cg.identifier.ccafsprojectpii as the field name
"headline": "February, 2017",
"url": "https://alanorth.github.io/cgspace-notes/2017-02/",
- "wordCount": "464",
+ "wordCount": "553",
"datePublished": "2017-02-07T07:04:52-08:00",
@@ -248,9 +248,26 @@ DELETE 1
2017-02-15
+2017-02-16
+
+
+- Looking at memory info from munin on CGSpace:
+
+
+
+
+
+- We are using only ~8GB of RAM for applications, and 16GB for caches!
+- The Linode machine we’re on has 24GB of RAM but only because that’s the only instance that had enough disk space for us (384GB)…
+- We should probably look into Google Compute Engine or Digital Ocean where we can get more storage without having to follow a linear increase in instance pricing for CPU/memory as well
+- Especially because we only use 2 out of 8 CPUs basically:
+
+
+
+
diff --git a/public/2017/02/cpu-week.png b/public/2017/02/cpu-week.png
new file mode 100644
index 000000000..405aa7070
Binary files /dev/null and b/public/2017/02/cpu-week.png differ
diff --git a/public/2017/02/meminfo_phisical-week.png b/public/2017/02/meminfo_phisical-week.png
new file mode 100644
index 000000000..0d9e85189
Binary files /dev/null and b/public/2017/02/meminfo_phisical-week.png differ
diff --git a/public/index.xml b/public/index.xml
index 00f443a06..1d243da67 100644
--- a/public/index.xml
+++ b/public/index.xml
@@ -96,8 +96,25 @@ DELETE 1
<h2 id="2017-02-15">2017-02-15</h2>
<ul>
-<li>Update rvm on DSpace Test and CGSpace as there was a <a href="https://github.com/justinsteven/advisories/blob/master/2017_rvm_cd_command_execution.md">security disclosure about versions <= 1.28.0</a></li>
-</ul>
+<li>Update rvm on DSpace Test and CGSpace as there was a <a href="https://github.com/justinsteven/advisories/blob/master/2017_rvm_cd_command_execution.md">security disclosure about versions less than 1.28.0</a></li>
+</ul>
+
+<h2 id="2017-02-16">2017-02-16</h2>
+
+<ul>
+<li>Looking at memory info from munin on CGSpace:</li>
+</ul>
+
+<p><img src="https://alanorth.github.io/cgspace-notes/cgspace-notes/2017/02/meminfo_phisical-week.png" alt="CGSpace meminfo" /></p>
+
+<ul>
+<li>We are using only ~8GB of RAM for applications, and 16GB for caches!</li>
+<li>The Linode machine we’re on has 24GB of RAM but only because that’s the only instance that had enough disk space for us (384GB)…</li>
+<li>We should probably look into Google Compute Engine or Digital Ocean where we can get more storage without having to follow a linear increase in instance pricing for CPU/memory as well</li>
+<li>Especially because we only use 2 out of 8 CPUs basically:</li>
+</ul>
+
+<p><img src="https://alanorth.github.io/cgspace-notes/cgspace-notes/2017/02/cpu-week.png" alt="CGSpace CPU" /></p>
-
diff --git a/public/post/index.xml b/public/post/index.xml
index a37532084..8117d35df 100644
--- a/public/post/index.xml
+++ b/public/post/index.xml
@@ -96,8 +96,25 @@ DELETE 1
<h2 id="2017-02-15">2017-02-15</h2>
<ul>
-<li>Update rvm on DSpace Test and CGSpace as there was a <a href="https://github.com/justinsteven/advisories/blob/master/2017_rvm_cd_command_execution.md">security disclosure about versions <= 1.28.0</a></li>
-</ul>
+<li>Update rvm on DSpace Test and CGSpace as there was a <a href="https://github.com/justinsteven/advisories/blob/master/2017_rvm_cd_command_execution.md">security disclosure about versions less than 1.28.0</a></li>
+</ul>
+
+<h2 id="2017-02-16">2017-02-16</h2>
+
+<ul>
+<li>Looking at memory info from munin on CGSpace:</li>
+</ul>
+
+<p><img src="https://alanorth.github.io/cgspace-notes/cgspace-notes/2017/02/meminfo_phisical-week.png" alt="CGSpace meminfo" /></p>
+
+<ul>
+<li>We are using only ~8GB of RAM for applications, and 16GB for caches!</li>
+<li>The Linode machine we’re on has 24GB of RAM but only because that’s the only instance that had enough disk space for us (384GB)…</li>
+<li>We should probably look into Google Compute Engine or Digital Ocean where we can get more storage without having to follow a linear increase in instance pricing for CPU/memory as well</li>
+<li>Especially because we only use 2 out of 8 CPUs basically:</li>
+</ul>
+
+<p><img src="https://alanorth.github.io/cgspace-notes/cgspace-notes/2017/02/cpu-week.png" alt="CGSpace CPU" /></p>
-
diff --git a/public/tags/notes/index.xml b/public/tags/notes/index.xml
index 136766cea..307886340 100644
--- a/public/tags/notes/index.xml
+++ b/public/tags/notes/index.xml
@@ -95,8 +95,25 @@ DELETE 1
<h2 id="2017-02-15">2017-02-15</h2>
<ul>
-<li>Update rvm on DSpace Test and CGSpace as there was a <a href="https://github.com/justinsteven/advisories/blob/master/2017_rvm_cd_command_execution.md">security disclosure about versions <= 1.28.0</a></li>
-</ul>
+<li>Update rvm on DSpace Test and CGSpace as there was a <a href="https://github.com/justinsteven/advisories/blob/master/2017_rvm_cd_command_execution.md">security disclosure about versions less than 1.28.0</a></li>
+</ul>
+
+<h2 id="2017-02-16">2017-02-16</h2>
+
+<ul>
+<li>Looking at memory info from munin on CGSpace:</li>
+</ul>
+
+<p><img src="https://alanorth.github.io/cgspace-notes/cgspace-notes/2017/02/meminfo_phisical-week.png" alt="CGSpace meminfo" /></p>
+
+<ul>
+<li>We are using only ~8GB of RAM for applications, and 16GB for caches!</li>
+<li>The Linode machine we’re on has 24GB of RAM but only because that’s the only instance that had enough disk space for us (384GB)…</li>
+<li>We should probably look into Google Compute Engine or Digital Ocean where we can get more storage without having to follow a linear increase in instance pricing for CPU/memory as well</li>
+<li>Especially because we only use 2 out of 8 CPUs basically:</li>
+</ul>
+
+<p><img src="https://alanorth.github.io/cgspace-notes/cgspace-notes/2017/02/cpu-week.png" alt="CGSpace CPU" /></p>
-
diff --git a/static/2017/02/cpu-week.png b/static/2017/02/cpu-week.png
new file mode 100644
index 000000000..405aa7070
Binary files /dev/null and b/static/2017/02/cpu-week.png differ
diff --git a/static/2017/02/meminfo_phisical-week.png b/static/2017/02/meminfo_phisical-week.png
new file mode 100644
index 000000000..0d9e85189
Binary files /dev/null and b/static/2017/02/meminfo_phisical-week.png differ