Let’s first talk about the reason I started looking for this. I have a couple of services running in Ubuntu including DBs like MySQL, MongoDB, etc. along with running nGinx and other services.
However, sometimes, I noticed that the memory consumption goes upwards and it’s wise to know which process could be responsible for this.
format is a single argument in the form of a blank-separated or comma-separated list, which offers a way to specify individual output columns.
pmem
the ratio of the process’s resident set size to the physical memory on the machine, expressed as a percentage.
pcpu
CPU utilization of the process in the “##.#” format. Currently, it is the CPU time used divided by the time the process has been running (cputime/real time ratio), expressed as a percentage.
pid
A number representing the process ID
args
Command with all its arguments as a string.
tail -n +2
Output lines starting to the second line
sort -rnk 1
r (reverse) n(numeric sort) by column 1 i.e., pmem
Has there been an instance that you are trying to load your site, say even a simple WordPress and it feels just so slow that you might not even get a proper response. You might just only end up seeing an error.
This is exactly what happened to me today. I have a Ubuntu VPS with 4GB RAM and all of a sudden I get emails from Jetpack saying my site appears to be down. It hit me with so many questions especially, if something happened to my VPS. Did I lose my data? Blah…Blah…
But then I thought, let me just jump into the terminal and see what’s going on. The very first thing I did is restart my Nginx Server.
sudo service nginx restart
Now that my server had restarted, I was still seeing weird responses to my pages and other services. It was as if the entire system was choked down. But my graphs were showing still a huge amount of memory left out. So I decided to dig deeper but before doing that, let’s hit the command of restarting the Ubuntu server.
sudo shutdown -r now
Once my system restarted, I went to first check the logs at Nginx to see if something got screwed up. But I didn’t find anything useful. So I went to check the logs of the php-fpm engine and this is what I found.
server reached pm.max_children setting (5), consider raising it
It hit me as to what happened all of a sudden and I remembered, it’s probably due to some of the changes I made to one of the Image Caching Server. Anyways, I started and digging around the error message, especially the setting for pm.max_children = 5
After spending sometime, I found the place for this setting in /etc/php/7.0/fpm/pool.d/www.conf
Now, this is where the tricky part begins, as you have to ensure that the settings you do are not going to hamper your server with overload as well as they are sufficient enough to handle the load. Before we jump into it, let’s understand what we are trying to do here.
The log message with pm.max_children; pm stand for process manager. This process manager is responsible for instantiating child processes to handle the requests sent over to php-fpm engine.
Here the above image explains all the required values that need to be tweaked to get optimum performance from the server. Let’s look at the current configuration which I am having:
pm.max_children
5
pm.start_servers
2
pm.min_spare_servers
1
pm.max_spare_servers
3
So, now I needed to ensure that my configurations are somewhat reasonable based on my VPS configuration. But in order to do so, I need to know the max capacity that I can expect my child processes to reach. So I executed this command to know the current memory being utilized by the child processes.
Now, once I hit the enter key, I got this result in my terminal
If you look closely, the max that one of the child processes reached was 89.00 Mb. So to compute the Approx. value of pm.max_children can be as simple as this:
pm.max_children = Total RAM dedicated to the webserver / Max of child process size
pm.max_children = 3948 / 89 = 44.36
Considering the memory for other processes, I believe it’s safe to say that I can easily set my pm.max_children to 40 at least.
pm.max_children
40
pm.start_servers
2
pm.min_spare_servers
1
pm.max_spare_servers
3
[09-May-2020 13:24:45] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 8 children, there are 0 idle, and 5 total children [09-May-2020 13:24:46] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 16 children, there are 0 idle, and 6 total children
As you can see above, I also had to adjust the values for pm.start_servers, pm.min_spare_servers, and pm.max_spare_servers else without doing, I was getting those warnings. Here are the latest values that I had set considering the warnings
pm.max_children
40
pm.start_servers
15
pm.min_spare_servers
15
pm.max_spare_servers
30
Please note that very high values may not do anything good for your system. It might even burden your system.
Before we dive into the commands for installing Wine, let’s first talk about what Wine is in General in the Linux World.
As described in Wine’s Site: Wine (originally an acronym for “Wine Is Not an Emulator”) is a compatibility layer capable of running Windows applications on several POSIX-compliant operating systems, such as Linux, macOS, & BSD. Instead of simulating internal Windows logic like a virtual machine or emulator, Wine translates Windows API calls into POSIX calls on-the-fly, eliminating the performance and memory penalties of other methods and allowing you to cleanly integrate Windows applications into your desktop.
In short, it allows you to run Win32.exe Applications built for Windows System on Linux.
Let’s look at the steps required for installing Wine 5.0 on a Ubuntu 18.04 LTS system using the apt-get package manager
1. Setup PPA
If this is a 64-bit system , then we need to enable the 32-bit architecture. Once done, then install the key used to sign the wine package
Time to install Wine packages from the apt repository. The –install-recommends option will install all the recommended packages by winehq stable versions on your Ubuntu system.