The Terminal will then ask you for you're password, type it and then press enter. Linuxmint 13 Medico comes with pluma rather than gedit, so a substitution was needed. It can run scripts, connect to our MySQL databases to get information, and hand the processed communication over to our web server to display. I guess it took me a two or three hours trying various other options, before I found the solution. Harri-P: You're most welcome. This brief tutorial shows students and new users how to install phpMyAdmin with Apache2, MariaDB and PHP 7. Terminal scares the newbies, but here, you'll see how magical terminal or comand promt whatever you call it is.
Currently on my Apache 2 Apache 2. I am asking specifically only for how to tune Apache 2. This is why this question is different than. JennyD It's even easier than that. Then, watch the Apache logs for troubles with MaxRequestWorkers and either increase, add more RAM, add CloudFlare, or add another web node. No need to do extremely intense load testing. Also, recognize that starting in Apache 2. So, if the free column said I had 13GB free, I would recommend giving Apache 11GB. If we encounter any database issue in the logs occasionally as in like 3 times in the logs over a 3 day period that it needs more memory, then we might consider that we only had 10GB to play with instead of 11GB in this case. If we encounter in the Apache logs that the server needs more MaxRequestWorkers, then that's a separate issue I'll address below. Look at the Average Process Size value and average that value out among the 5 times you ran that. Now do the following math, and be sure to convert GB to MB as necessary so that all the numbers are in MB values. So, either multiply times 1024 or divide by 1024, depending on which way you need to go. I then provide another 1GB in some extra buffer space for the OS in case it needs it. That means I would have a Baseline Free of 12GB. Now I must convert it from GB to MB, and so I multiply 12 x 1024 and get 12288. The 12288 MB is my Baseline Free value. In my case I saw that the Average Process Size was 21MB. Now, it's common that sysops round down this value, and so I got 580. This parameter defaults to 256 if not present, but needs to be the same value as MaxRequestWorkers or you'll get an error. This is how long you can send or receive from the server before it times out. You have to also keep in mind a file upload or file download, such as if you have a website where people can upload or download CSV or other large files, for instance. And you need to keep in mind a busy database server and where you might need to provide some time before pages timeout. The smaller you make that Timeout variable, the more available the web server is to receive new connections. Note, however, that setting this value too low may cause havoc with PHP session variables, although not with browser session-based cookies. So, for instance, a value of 300 5 minutes might be good for a web server that relies on PHP session variables for web app workflow instead of browser session cookies. A value of 45 might be good for a web server that serves up nothing more than static advertising landing pages, but would be terrible for a server that needs to use PHP session variables a great deal. So, edit the Timeout parameter in this file to the amount you need. This may take some testing with all your web pages to see if the value is too low. It's probably a good idea, however, to not set it higher than 300 unless you're seeing problems in large file uploads or large file downloads. If you did something wrong, Apache will likely tell you about it the moment you start it again, and you can rectify it. Look for a complaint about needing MaxRequestWorkers and recently since you restarted the web server. If you see that even with an optimal MaxRequestWorkers setting, then you're likely needing more firepower for your websites or web applications. You'll need to check on it over the course of 2-3 weeks and look for MaxRequestWorker issues in the Apache error logs. From that, you can make a decision on optimization see step 10. You can also install Munin with apt on Ubuntu and look at the Apache performance over time and plot an idea of growth before you decide you need to do anything about the amount of traffic the web server is handling. Moderator I need formatting help on this answer. Step 7 was supposed to be conf file with indents. Step 11 wasn't supposed to be indented. Code commands that start with sudo need to show as code, not as normal text. I followed the documentation on formatting, but still struggle here. If each one takes up 50MB just picking a random number , then every 20 request workers you have in use at once i. However, you can't use up all the RAM for apache, you need to reserve some for other things running on there. Also leaving some spare RAM can be helpful for performance as the OS will use it to cache things and speed up performance though it may be preferable to not run out of connections as compared to the server being extra quick as the site will appear slow while users' browsers wait for a connection to come available if they get all used up.
