<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
Jason,<br>
<br>
This is excellent! I, for one, am excited that someone is looking
into this subject deeply. I've been wanting to migrate to a newer
version of PostgreSQL from quite some time. We have some test
machines running Evergreen on PG 10 but they are not getting the
thorough testing that I'd like to be certain it's ready for
production. So, thank you. Thank you very much!<br>
<br>
In order to configure PG to use 40% of the server's hardware, are
you focusing on settings?:<br>
<br>
<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">work_mem
max_connections
effective_cache_size
default_statistics_target
constraint_exclusion
checkpoint_completion_target
wal_buffers
shared_buffers
maintenance_work_mem</code></pre>
<br>
And kernel setting:<br>
<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">vm.overcommit_memory
</code></pre>
Or something else?<br>
<br>
I think it's a good idea to test the same version of Evergreen, like
you said. And the latest version makes the most sense.<br>
<br>
<pre class="moz-signature" cols="72">-Blake-
Conducting Magic
Can consume data in any format
MOBIUS
</pre>
<div class="moz-cite-prefix">On 7/21/2021 8:53 AM, Jason Stephenson
via Evergreen-dev wrote:<br>
</div>
<blockquote type="cite"
cite="mid:5607ff61-fee7-fbc6-dab3-e65f1acb69bb@sigio.com">Hello,
all.
<br>
<br>
As some of you are aware, I have been running Evergreen against
various PostgreSQL releases on an old email server that has 128 GB
of RAM and 8TB of disk space. I currently have PostgreSQL
versions 9.6 through 13 installed.
<br>
<br>
During my testing, I have identified a few areas where Evergreen
database performance is slower on newer Pg versions and other
areas where it is faster.
<br>
<br>
I am presently setting up to use the plprofiler extension
(<a class="moz-txt-link-freetext" href="https://github.com/bigsql/plprofiler">https://github.com/bigsql/plprofiler</a>) to test these areas,
beginning with those where I know that performance degrades in
PostgreSQL version greater than 10.
<br>
<br>
To make the test fair, I am loading a dump of CW MARS' production
database from Sunday, July 11, 2021 into the various Pg instances.
Since we are currently on Evergreen 3.5.3, I intend to also run a
database upgrade script on each instance.
<br>
<br>
I have a question regarding the database upgrade: Should I upgrade
to Evergreen 3.7.1 or to an arbitrary commit on the master branch,
i.e. the one that is current as of the time that I generate the db
upgrade?
<br>
<br>
I also intend to use optimization settings on the database
instance being tested. I presently have 2 of the instances
configured to use roughly 40% of the server's capabilities and the
other instances are left at the default settings. I may continue
with the 40% optimization or go with settings that will utilize
more of the hardware for just the instance being tested and either
shut off or run the other instances with default settings.
<br>
<br>
If anyone has any additional ideas of things that should be tested
or would like to help devise a script to more thoroughly test the
Evergreen database, let me know.
<br>
<br>
Cheers,
<br>
Jason
<br>
_______________________________________________
<br>
Evergreen-dev mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:Evergreen-dev@list.evergreen-ils.org">Evergreen-dev@list.evergreen-ils.org</a>
<br>
<a class="moz-txt-link-freetext" href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-dev">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-dev</a>
<br>
</blockquote>
<br>
</body>
</html>