Configure PSQL Server Memory Usage

Configure PSQL Server Memory Usage

Version: Any
Release Date: 12/17/2021

Q - Can you tell us why PSQL process is taking up so much memory?  Is there anything we can do? See sample screen below:


A - PSQL server by default can take up about 60ish% of the server memory. This is adjustable. You can bring up PCC on the PSQL server. Right click on the server node and choose “Properties.” See sample screen below:


In the Properties window, go to “Performance tuning.” You will see the default value for “Max MicroKernel Memory Usage” is set to “60” which means 60% of the server memory. See below:


That 60% is what we call the Level 2 cache, which is subject to compression so the PSQL server can hold more data in memory. The Level 1 cache is the value 3247 in Cache Allocation Size in MB, which is about 3.2GB in this case. Level 1 cache is allocated upon startup by the PSQL engine and it is not compressed, so level 1 cache is faster than level 2. Level 2 cache,  even though it is compressed, is still much faster than accessing data from disk. Therefore, you can adjust the values in “Cache Allocation Size in MB” and “Max MicroKernel Memory Usage” to balance between performance and memory usage. Generally speaking, more memory will help out the performance.

In your case, I see you also share Microsoft’s SQL server with PSQL database engine. There are several instances of your SQL server which also takes a significant amount of memory. I see you have several options here: (1) Do nothing. In your example, the server still has some free memory; (2) If you are running out of memory and you can’t control the memory growth from services like the SQL server, then you may want to consider moving SQL servers to a different server; (3) If moving SQL servers is too much efforts, then adding more memory to this server is a good option; (4) Lastly, you can reduce PSQL memory usage by adjusting its memory usage as explained above. This may be easy to do, but not necessary your best option. Your PSQL performance can be affected. But we won’t know the magnitude until you try.

The bottom line is you need sufficient memory to run your server. The above explanations should give you enough information on what to do next. 


EMK


    • Related Articles

    • Can I Dynamically Adjust Elliott / PSQL 11 Server Memory?

      In the virtual server environment, it is very easy to adjust the server's memory in order to better suit your requirements and more efficiently use the server hardware. However, it is important for you to be aware that the PSQL 11 engine license can ...
    • Do I Need to Change PSQL Server Engine Default Parameters After Installing It?

      Q - I am installing a PSQL server engine for my client. Do I need to change any PSQL parameters after the installation? A - Generally speaking, you don't need to change PSQL parameters after the installation. There are two optional changes you can ...
    • A Case to Optimize PSQL Query Performance with INNER JOIN SYCONTCT & SYCONREL Tables

      Release Date: 11/29/2023 Version: 7.x & Up Q - With our custom web application, we attempt to find an existing customer and associated contact when creating new customers via the Elliott web services. We are finding the customer just fine, but when I ...
    • Hardware Recommendations for Your PSQL Database Server

      Release Date: 10/10/2017 This article was written by Bill Bach and is provided at the courtesy of Goldstar Software. Recommendations for hardware for your PSQL database environment One of the most common questions we get is “What kind of hardware ...
    • Does Elliott Support Windows Server 2019?

      Release Date: 7/8/2019 Version: 8.5 Q: Does Elliott and PSQL support Windows Server 2019? A: We tested the latest Elliott 8.5 on server 2019 and it works. We can’t guarantee that the older Elliott versions will work with server 2019. In addition, per ...