From 9520c8b49069f40cce57684e89ba8ca135780bf5 Mon Sep 17 00:00:00 2001
From: Alan Orth <alan.orth@gmail.com>
Date: Thu, 23 Nov 2017 17:18:45 +0200
Subject: [PATCH] Update notes for 2017-11-23

---
 content/post/2017-11.md   |  3 +++
 public/2017-11/index.html |  9 ++++++---
 public/sitemap.xml        | 10 +++++-----
 3 files changed, 14 insertions(+), 8 deletions(-)

diff --git a/content/post/2017-11.md b/content/post/2017-11.md
index d8f04a377..1b0bdd84c 100644
--- a/content/post/2017-11.md
+++ b/content/post/2017-11.md
@@ -826,3 +826,6 @@ $ grep 70.32.83.92 dspace.log.2017-11-23 | grep -o -E 'session_id=[A-Z0-9]{32}'
 
 - I'm wondering if REST works differently, or just doesn't log these sessions?
 - I wonder if they are measurable via JMX MBeans?
+- I came across some interesting PostgreSQL tuning advice for SSDs: https://amplitude.engineering/how-a-single-postgresql-config-change-improved-slow-query-performance-by-50x-85593b8991b0
+- Apparently setting `random_page_cost` to 1 is "common" advice for systems running PostgreSQL on SSD (the default is 4)
+- So I deployed this on DSpace Test and will check the Munin PostgreSQL graphs in a few days to see if anything changes
diff --git a/public/2017-11/index.html b/public/2017-11/index.html
index 926b38a5e..cacea1d82 100644
--- a/public/2017-11/index.html
+++ b/public/2017-11/index.html
@@ -38,7 +38,7 @@ COPY 54701
 
 <meta property="article:published_time" content="2017-11-02T09:37:54&#43;02:00"/>
 
-<meta property="article:modified_time" content="2017-11-22T10:20:44&#43;02:00"/>
+<meta property="article:modified_time" content="2017-11-23T12:23:19&#43;02:00"/>
 
 
 
@@ -86,9 +86,9 @@ COPY 54701
   "@type": "BlogPosting",
   "headline": "November, 2017",
   "url": "https://alanorth.github.io/cgspace-notes/2017-11/",
-  "wordCount": "4773",
+  "wordCount": "4825",
   "datePublished": "2017-11-02T09:37:54&#43;02:00",
-  "dateModified": "2017-11-22T10:20:44&#43;02:00",
+  "dateModified": "2017-11-23T12:23:19&#43;02:00",
   "author": {
     "@type": "Person",
     "name": "Alan Orth"
@@ -1074,6 +1074,9 @@ $ grep -c com.atmire.utils.UpdateSolrStatsMetadata dspace.log.2017-11-19
 <ul>
 <li>I&rsquo;m wondering if REST works differently, or just doesn&rsquo;t log these sessions?</li>
 <li>I wonder if they are measurable via JMX MBeans?</li>
+<li>I came across some interesting PostgreSQL tuning advice for SSDs: <a href="https://amplitude.engineering/how-a-single-postgresql-config-change-improved-slow-query-performance-by-50x-85593b8991b0">https://amplitude.engineering/how-a-single-postgresql-config-change-improved-slow-query-performance-by-50x-85593b8991b0</a></li>
+<li>Apparently setting <code>random_page_cost</code> to 1 is &ldquo;common&rdquo; advice for systems running PostgreSQL on SSD (the default is 4)</li>
+<li>So I deployed this on DSpace Test and will check the Munin PostgreSQL graphs in a few days to see if anything changes</li>
 </ul>
 
   
diff --git a/public/sitemap.xml b/public/sitemap.xml
index 5a33219f5..82ec12c7f 100644
--- a/public/sitemap.xml
+++ b/public/sitemap.xml
@@ -4,7 +4,7 @@
   
   <url>
     <loc>https://alanorth.github.io/cgspace-notes/2017-11/</loc>
-    <lastmod>2017-11-22T10:20:44+02:00</lastmod>
+    <lastmod>2017-11-23T12:23:19+02:00</lastmod>
   </url>
   
   <url>
@@ -134,7 +134,7 @@
   
   <url>
     <loc>https://alanorth.github.io/cgspace-notes/</loc>
-    <lastmod>2017-11-22T10:20:44+02:00</lastmod>
+    <lastmod>2017-11-23T12:23:19+02:00</lastmod>
     <priority>0</priority>
   </url>
   
@@ -145,7 +145,7 @@
   
   <url>
     <loc>https://alanorth.github.io/cgspace-notes/tags/notes/</loc>
-    <lastmod>2017-11-22T10:20:44+02:00</lastmod>
+    <lastmod>2017-11-23T12:23:19+02:00</lastmod>
     <priority>0</priority>
   </url>
   
@@ -157,13 +157,13 @@
   
   <url>
     <loc>https://alanorth.github.io/cgspace-notes/post/</loc>
-    <lastmod>2017-11-22T10:20:44+02:00</lastmod>
+    <lastmod>2017-11-23T12:23:19+02:00</lastmod>
     <priority>0</priority>
   </url>
   
   <url>
     <loc>https://alanorth.github.io/cgspace-notes/tags/</loc>
-    <lastmod>2017-11-22T10:20:44+02:00</lastmod>
+    <lastmod>2017-11-23T12:23:19+02:00</lastmod>
     <priority>0</priority>
   </url>