Hey Mihai,
Most of VPS host can run Wordpress site with good performance, the task for that is very easy, you need to configure your VPS correctly to have the best performance. But
In the process of working with WordPress, I realized something very important greatly affected the performance of websites that using WordPress cms. That is Wordpress is often query API to retrieve information on WordPress.org about updates for their new themes and plugins. Therefore the connected line to wordpress.org is extremely important influence WordPress site speed, especially WordPress admin page and we can use this factor to check if our VPS is working as well with Wordpress or not.
Choosing VPS that suitable to WordPress
Use Ping to test the quality of VPS network. Response time of the network is very important in this case, so we will use the Ping command to test the response time of the server to WordPress.org (including wordpress.org and api.wordpress. org)
Code:
ping -c 100 wordpress.org
ping -c 100 api.wordpress.org
I used 100 times and the result is pretty correct
and my results on a VPS is as following
The result of Ping to wordpress.org
Code:
[root@server ~]# ping -c 10 wordpress.org
PING wordpress.org (66.155.40.250) 56(84) bytes of data.
64 bytes from 66.155.40.250: icmp_seq=1 ttl=55 time=85.0 ms
64 bytes from 66.155.40.250: icmp_seq=2 ttl=55 time=84.9 ms
64 bytes from 66.155.40.250: icmp_seq=3 ttl=55 time=85.0 ms
64 bytes from 66.155.40.250: icmp_seq=4 ttl=55 time=85.0 ms
64 bytes from 66.155.40.250: icmp_seq=5 ttl=55 time=85.0 ms
64 bytes from 66.155.40.250: icmp_seq=6 ttl=55 time=85.0 ms
64 bytes from 66.155.40.250: icmp_seq=7 ttl=55 time=85.0 ms
64 bytes from 66.155.40.250: icmp_seq=8 ttl=55 time=85.0 ms
64 bytes from 66.155.40.250: icmp_seq=9 ttl=55 time=85.0 ms
64 bytes from 66.155.40.250: icmp_seq=10 ttl=55 time=85.0 ms
...........................
--- wordpress.org ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9096ms
rtt min/avg/max/mdev = 84.990/85.028/85.067/0.186 ms
In the parameters above, then you are most interested in the following parameters:
packet loss : let you know how many % ping times failed, this number more high more bad VPS network you get.
rtt min/avg/max/mdev you need to concentrate on the value of
avg and
mdev, if 85.028 and 0.186 ms is more small you get better speed of your VPS.
The result of Ping to api.wordpress.org
Code:
[root@server ~]# ping -c 10 api.wordpress.org
PING api.wordpress.org (66.155.40.188) 56(84) bytes of data.
64 bytes from 66.155.40.188: icmp_seq=1 ttl=55 time=87.0 ms
64 bytes from 66.155.40.188: icmp_seq=2 ttl=55 time=87.3 ms
64 bytes from 66.155.40.188: icmp_seq=3 ttl=55 time=87.1 ms
64 bytes from 66.155.40.188: icmp_seq=4 ttl=55 time=87.1 ms
64 bytes from 66.155.40.188: icmp_seq=5 ttl=55 time=87.2 ms
64 bytes from 66.155.40.188: icmp_seq=6 ttl=55 time=87.2 ms
64 bytes from 66.155.40.188: icmp_seq=7 ttl=55 time=87.2 ms
64 bytes from 66.155.40.188: icmp_seq=8 ttl=55 time=87.0 ms
64 bytes from 66.155.40.188: icmp_seq=9 ttl=55 time=87.1 ms
64 bytes from 66.155.40.188: icmp_seq=10 ttl=55 time=87.0 ms
--- api.wordpress.org ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9101ms
rtt min/avg/max/mdev = 87.069/87.160/87.305/0.241 ms
You can change 100 to your number for how many times you want to ping to wordpress.org
If possible, let us know what is your result when Ping to Wordpress site from your VPS.
Hope it helps!
