• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Please beaware of a breaking change in the REST API on the next Plesk release (18.0.62).
    Starting from Plesk Obsidian 18.0.62, requests to REST API containing the Content-Type header with a media-type directive other than “application/json” will result in the HTTP “415 Unsupported Media Type” client error response code. Read more here

Question how to improve WP performance on nginx server vs

larryk

Regular Pleskian
hello,

this is in general, what should I "check for" or what plesk server settings should I be concerned about to get the most performance on my server....

AS OPPOSED TO, setting that can be done in wp-config.php on the WP install?
things mentioned here: https://codex.wordpress.org/Editing_wp-config.php


If you know of "things, settings, configs, etc" that can or do improve performance at server level for Plesk nginx config... WOULD LOVE to know what you did :)

I'm trying to learn, figure out, and tweak the msyql DB... but a little lost on what is good, better or actually makes a positive difference? Working with my support team:


Code:
I changed the following in /etc/my.cnf:

    key_buffer = 5G ( was 1G)innodb_buffer_pool_size = 1G (was 512MB)


I have added the following configuration to /etc/httpd/conf.d/fcgid.conf:

    <IfModule !mod_fastcgi.c>   
AddHandler fcgid-script fcg fcgi fpl</IfModule>
##Apache Event Default Settings (overrides main httpd.conf)KeepAlive            
OnKeepAliveTimeout        2
MaxKeepAliveRequests    500
<IfModule event.c>ThreadsPerChild        25
ServerLimit            16
MaxRequestWorkers      400
StartServers            6
MinSpareThreads        150
MaxSpareThreads        400
MaxRequestsPerChild    10000</IfModule>

<IfModule mod_fcgid.c>
FcgidMaxRequestLen                      1073741824
FcgidOutputBufferSize                  1073741824
FcgidMinProcessesPerClass              0
FcgidMaxRequestsPerProcess              0
FcgidInitialEnv PHP_FCGI_MAX_REQUESTS  0
FcgidInitialEnv PHP_FCGI_CHILDREN      0
FcgidMaxProcesses                      320
FcgidMaxProcessesPerClass              160
FcgidFixPathinfo                        1
FcgidIdleTimeout                        3
FcgidBusyTimeout                        300
FcgidProcessLifeTime                    300
FcgidIOTimeout                          300
FcgidIdleScanInterval                  1
FcgidErrorScanInterval                  1
FcgidZombieScanInterval                1</IfModule>


This is the default configuration:

    LoadModule fcgid_module modules/mod_fcgid.so
<IfModule mod_fcgid.c>
<IfModule !mod_fastcgi.c>   
AddHandler fcgid-script fcg fcgi fpl</IfModule>

 FcgidIPCDir /var/run/mod_fcgid/sock
FcgidProcessTableFile /var/run/mod_fcgid/fcgid_shm
FcgidIdleTimeout 40
FcgidProcessLifeTime 30
FcgidMaxProcesses 20
FcgidMaxProcessesPerClass 8
FcgidMinProcessesPerClass 0
FcgidConnectTimeout 30
FcgidIOTimeout 90 
FcgidInitialEnv RAILS_ENV production
  FcgidIdleScanInterval 10
</IfModule>


this came from mysqltuner:

Code:
I have installed MySQL tuner on your server, and it has returned the following results:

    -------- Recommendations ---------------------------------------------------------------------------General recommendations:   
Control warning line(s) into /var/log/mariadb/mariadb.log file   
Restrict Host for user@% to user@SpecificDNSorIp  
MySQL started within last 24 hours - recommendations may be inaccurate  
Configure your accounts with ip or subnets only, then update your configuration with skip-name-resolve=1  
When making adjustments, make tmp_table_size/max_heap_table_size equal  
Reduce your SELECT DISTINCT queries which have no LIMIT clause  
Set thread_cache_size to 4 as a starting valueVariables to adjust:  
query_cache_type (=0)  
sort_buffer_size (> 2M)  
read_rnd_buffer_size (> 256K)  
tmp_table_size (> 96M)  
max_heap_table_size (> 96M)  
thread_cache_size (start at 4) 
 innodb_file_per_table=ON  
innodb_buffer_pool_size (>= 1G) if possible.  
innodb_log_file_size should be equals to 1/4 of buffer pool size (=256M) if possible.

So if you are a mySQL admin -- would love any feedback :)



I have this:
CentOS Linux 7.2.1511 (Core)‬
Plesk Onyx Version 17.0.17 Update #13, last updated on Jan 23, 2017 03:47 AM
My Dedicated server:
CPU: Intel Xeon E3-1271 v3 Quad-Core RAM: 32GB DDR3 SDRAM
Primary Hard Drive: 2 x SSD Software RAID, SSD Drive Size: 250GB Crucial SSD (MLC)

note: A 3% performance boost is awesome.... a 10% boost is even better :)
 
Last edited:
Back
Top