From 56a001943d15488de63b200210588b973057c205 Mon Sep 17 00:00:00 2001 From: Alan Orth Date: Fri, 24 Nov 2017 00:59:11 +0200 Subject: [PATCH] Update notes for 2017-11-23 --- content/post/2017-11.md | 1 + public/2017-11/index.html | 7 ++++--- public/sitemap.xml | 10 +++++----- 3 files changed, 10 insertions(+), 8 deletions(-) diff --git a/content/post/2017-11.md b/content/post/2017-11.md index 1b0bdd84c..6f17dfbe1 100644 --- a/content/post/2017-11.md +++ b/content/post/2017-11.md @@ -826,6 +826,7 @@ $ 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 did some tests locally and I don't see the sessionCounter incrementing after making requests to REST, but it does with XMLUI and OAI - 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 cacea1d82..681673dd8 100644 --- a/public/2017-11/index.html +++ b/public/2017-11/index.html @@ -38,7 +38,7 @@ COPY 54701 - + @@ -86,9 +86,9 @@ COPY 54701 "@type": "BlogPosting", "headline": "November, 2017", "url": "https://alanorth.github.io/cgspace-notes/2017-11/", - "wordCount": "4825", + "wordCount": "4849", "datePublished": "2017-11-02T09:37:54+02:00", - "dateModified": "2017-11-23T12:23:19+02:00", + "dateModified": "2017-11-23T17:18:45+02:00", "author": { "@type": "Person", "name": "Alan Orth" @@ -1074,6 +1074,7 @@ $ grep -c com.atmire.utils.UpdateSolrStatsMetadata dspace.log.2017-11-19