Publish an ideal Server Tuning/Configuration Table so Users can get an best fit starter for different ranges of processor levels or usage
You should have a guide for ideal server configurations and settings which Users can adopt easily.
So if a server has 3 CPUs and 4Gigs of RAM and is running Wordpress sites of 2 Gigs
The recommended server settings are xxxx.....
Presently these settings are on forums and there area a gazillion contradictory advice.
Parallels is ideally placed to establish such guides in the context of the server management environment.
mike
Unfortunately, we have to close your request, because over the years it has not become quite popular for further implementation.
—
IG
-
trialotto commented
@Sergey, @Everyone,
In a strange fashion, this feedback post is starting with the wrong topic (tuning for Wordpress), but still is touching a core issue (optimal Plesk configuration).
Personally, I do agree with Sergey that no (single) optimal configuration set exists.
Configuration depends on various factors.
However, in daily practice, no or little disagreement exists about configuration sets that are to be considered as "wrong".
Starting with this (agreed upon) subset, one could improve the general configuration of Plesk, that is the standard out-of-the-box configuration.
In general, Plesk does not make full use of all capacities and functions of packages installed.
The out-of-the-box configuration is (in a sense) using the "unconfigured" method, for the sake of safeguarding and optimizing Plesk customer´s ability to tweak performance.
As stated earlier, it is not an option to implement the "optimal" method for configuration, given the multiplicity of factors (and their interaction) that should be taken into consideration.
It IS an option to implement the "prevent wrong" method for configuration, being
- leave configuration as-is,
- apply specific configuration IF and ONLY IF other settings would yield undesired performanceand note that "undesired" is something (completely) different than "suboptimal".
It really is not a shame to have a working Plesk installation with suboptimal performance.
It really IS a shame to have a non-working Plesk installation, due to undesired settings.
In short, I would propose to start from the question: which configuration settings are "wrong"?
Personally, I think that a simple script either adding specific "desired" settings or removing specific "undesired" settings can be easily constructed and implemented in Plesk.
After all, most of the Plesk components already have a config check tool.
Hope the above helps...
Kind regards....
-
Woolfie commented
Love to have those yesterday.
I see Plesk comes budled with tons of functionality which i am just getting to learn how to use.
Basic Tuning Tools is the best start point - not least switching on and some of the great core functionality exploys more processing resources.....so getting the basic server working optimally gives one a great basis on which to beging planning decisions about expanding the use of such functions.
thanks for listening
-
Definitely agree. We do have some thoughts how to tune server defaults
-
Woolfie commented
"ideal" is probably the wrong word...."suggested" may be better.
You have really underlined why you are best placed to offer such information. Not least it helps your Users get the best out of Plesk.
Yes to the less-than-ideal suggestion - I am not saying it is a replacement for local tweaking.
Because of this information hoarding by the experts - there a lot of Users who do not anything like utilise a fraction of the functionality offered by Plesk
So it would be in your interest to research and offer assists on optimising and tuning. It makes your product way more attractive to competitors who dont and similarly attract more new entrants into using your technology [since it will be simpler to employ].