Wdcp Memory Optimization Method

WdcpMemory Optimization Method
After changing the vps Space Provider several times, it is estimated that no one has me so frequently. I have installed wdcp using centOS5. I have already installed wdcp very well, and I am also proficient in wdcp panel, I have raised several minor problems found during usage. After installing the 2.4 installation package provided by the Forum, the panel file management does not have the upload option, which is available only after the Panel is upgraded online, the upload option supports multi-File Upload, but I have tried several wdcp panels of different vps. If you have selected multiple files, click OK, only the first file will be uploaded. Other files selected below will not be uploaded. This is the first small problem found.

The second problem is the firewall's iptables access rule configuration.
At first, I thought it was okay to add access rules. After the system was restarted, those rules were gone. Then, I checked that there was an inconspicuous save link that was not followed, fortunately, I only have two rules, not too many. I can reset them soon. We recommend that you save them as buttons or put them under the page, the common habit is that there is a button below to save. Or you can simply add rules without saving them.

In fact, wdcp can save a lot of memory, but it only sets php and mysql by default during wdcp installation. Therefore, after the wdcp is installed, the memory occupied a lot. In fact, after wdcp is installed, I can use only one web engine. I chose apache. The memory used in php settings is half that of the default one, and the number of mysql connections is also a little small. With the optimization solution, my memory is basically less than 140, the minimum speed is 40-70, and the website efficiency remains unchanged. You can also try it. Of course, if it is not suitable for a website with high traffic, please smile. Add a server security sharing:

I just saw a post about an IDC from the top post. In fact, I have used wdcp for several days to find these security problems. It is true that the ssh password is too simple and there are major risks, you can check in the system log that the default ssh port is 22. I used to see in the log that someone tried to crack my root password by using hard cracking, I tried to isolate these hacker IP addresses by using firewall rules, but there were more than one attack. To solve the problem, I decided to change the ssh port, wdcp also provides the ssh port modification function. If you change the port, you also need to add the corresponding rules in the firewall. Otherwise, you will not be able to access it, we recommend that you change the background logon port of wdcp to be more secure.

This tutorial from wdlinux Forum http://www.wdlinux.cn/bbs/ reprint please note!