Update notes for 2019-03-31

This commit is contained in:
Alan Orth 2019-03-31 13:34:41 +03:00
parent 243007eefd
commit 5c6c5e78f8
Signed by: alanorth
GPG Key ID: 0FB860CC9C45B1B9
3 changed files with 29 additions and 8 deletions

View File

@ -1012,4 +1012,12 @@ $ time http --print h 'https://cgspace.cgiar.org/rest/items?expand=metadata,bits
0.25s user 0.06s system 1% cpu 15.947 total 0.25s user 0.06s system 1% cpu 15.947 total
``` ```
- I did some research on dedicated servers to potentially replace Linode for CGSpace stuff and it seems Hetzner is pretty good
- This [PX62-NVME system](https://www.hetzner.com/dedicated-rootserver/px62-nvme) looks great an is half the price of our current Linode instance
- It has 64GB of ECC RAM, six core Xeon processor from 2018, and 2x960GB NVMe storage
- The alternative of staying with Linode and using dedicated CPU instances with added block storage gets expensive quickly if we want to keep more than 16GB of RAM (do we?)
- Regarding RAM, our JVM heap is 8GB and we leave the rest of the system's 32GB of RAM to PostgreSQL and Solr buffers
- Seeing as we have 56GB of Solr data it might be better to have more RAM in order to keep more of it in memory
- Also, I know that the Linode block storage is a major bottleneck for Solr indexing
<!-- vim: set sw=2 ts=2: --> <!-- vim: set sw=2 ts=2: -->

View File

@ -25,7 +25,7 @@ I think I will need to ask Udana to re-copy and paste the abstracts with more ca
<meta property="og:type" content="article" /> <meta property="og:type" content="article" />
<meta property="og:url" content="https://alanorth.github.io/cgspace-notes/2019-03/" /> <meta property="og:url" content="https://alanorth.github.io/cgspace-notes/2019-03/" />
<meta property="article:published_time" content="2019-03-01T12:16:30&#43;01:00"/> <meta property="article:published_time" content="2019-03-01T12:16:30&#43;01:00"/>
<meta property="article:modified_time" content="2019-03-31T09:54:18&#43;03:00"/> <meta property="article:modified_time" content="2019-03-31T10:20:45&#43;03:00"/>
<meta name="twitter:card" content="summary"/> <meta name="twitter:card" content="summary"/>
<meta name="twitter:title" content="March, 2019"/> <meta name="twitter:title" content="March, 2019"/>
@ -55,9 +55,9 @@ I think I will need to ask Udana to re-copy and paste the abstracts with more ca
"@type": "BlogPosting", "@type": "BlogPosting",
"headline": "March, 2019", "headline": "March, 2019",
"url": "https://alanorth.github.io/cgspace-notes/2019-03/", "url": "https://alanorth.github.io/cgspace-notes/2019-03/",
"wordCount": "6418", "wordCount": "6563",
"datePublished": "2019-03-01T12:16:30&#43;01:00", "datePublished": "2019-03-01T12:16:30&#43;01:00",
"dateModified": "2019-03-31T09:54:18&#43;03:00", "dateModified": "2019-03-31T10:20:45&#43;03:00",
"author": { "author": {
"@type": "Person", "@type": "Person",
"name": "Alan Orth" "name": "Alan Orth"
@ -1321,6 +1321,19 @@ sys 0m2.551s
0.25s user 0.06s system 1% cpu 15.947 total 0.25s user 0.06s system 1% cpu 15.947 total
</code></pre> </code></pre>
<ul>
<li>I did some research on dedicated servers to potentially replace Linode for CGSpace stuff and it seems Hetzner is pretty good
<ul>
<li>This <a href="https://www.hetzner.com/dedicated-rootserver/px62-nvme">PX62-NVME system</a> looks great an is half the price of our current Linode instance</li>
<li>It has 64GB of ECC RAM, six core Xeon processor from 2018, and 2x960GB NVMe storage</li>
<li>The alternative of staying with Linode and using dedicated CPU instances with added block storage gets expensive quickly if we want to keep more than 16GB of RAM (do we?)</li>
<li>Regarding RAM, our JVM heap is 8GB and we leave the rest of the system&rsquo;s 32GB of RAM to PostgreSQL and Solr buffers</li>
<li>Seeing as we have 56GB of Solr data it might be better to have more RAM in order to keep more of it in memory</li>
<li>Also, I know that the Linode block storage is a major bottleneck for Solr indexing</li>
</ul></li>
</ul>
<!-- vim: set sw=2 ts=2: --> <!-- vim: set sw=2 ts=2: -->

View File

@ -4,7 +4,7 @@
<url> <url>
<loc>https://alanorth.github.io/cgspace-notes/2019-03/</loc> <loc>https://alanorth.github.io/cgspace-notes/2019-03/</loc>
<lastmod>2019-03-31T09:54:18+03:00</lastmod> <lastmod>2019-03-31T10:20:45+03:00</lastmod>
</url> </url>
<url> <url>
@ -214,7 +214,7 @@
<url> <url>
<loc>https://alanorth.github.io/cgspace-notes/</loc> <loc>https://alanorth.github.io/cgspace-notes/</loc>
<lastmod>2019-03-31T09:54:18+03:00</lastmod> <lastmod>2019-03-31T10:20:45+03:00</lastmod>
<priority>0</priority> <priority>0</priority>
</url> </url>
@ -225,7 +225,7 @@
<url> <url>
<loc>https://alanorth.github.io/cgspace-notes/tags/notes/</loc> <loc>https://alanorth.github.io/cgspace-notes/tags/notes/</loc>
<lastmod>2019-03-31T09:54:18+03:00</lastmod> <lastmod>2019-03-31T10:20:45+03:00</lastmod>
<priority>0</priority> <priority>0</priority>
</url> </url>
@ -237,13 +237,13 @@
<url> <url>
<loc>https://alanorth.github.io/cgspace-notes/posts/</loc> <loc>https://alanorth.github.io/cgspace-notes/posts/</loc>
<lastmod>2019-03-31T09:54:18+03:00</lastmod> <lastmod>2019-03-31T10:20:45+03:00</lastmod>
<priority>0</priority> <priority>0</priority>
</url> </url>
<url> <url>
<loc>https://alanorth.github.io/cgspace-notes/tags/</loc> <loc>https://alanorth.github.io/cgspace-notes/tags/</loc>
<lastmod>2019-03-31T09:54:18+03:00</lastmod> <lastmod>2019-03-31T10:20:45+03:00</lastmod>
<priority>0</priority> <priority>0</priority>
</url> </url>