Portal Home > Knowledgebase > Articles Database > how to improve the response time ?
how to improve the response time ?
Posted by ttgt, 02-04-2015, 09:28 AM |
Hi,
even my server load is not not high(0.x~2),
but when i browse my sites,
i feel it may take some seconds to do the first loading,
is any way to improve the response time on my cloudlinux/cpanel server?
|
Posted by zozo6015, 02-04-2015, 09:34 AM |
You may set up some caching and cache expiration for static files. Usually that will make things slightly faster.
|
Posted by mandrei99, 02-09-2015, 07:22 PM |
Wow. Sounds like you really should run your website through https://developers.google.com/speed/pagespeed/insights/ and see what they have to say. From your descrition, it looks like it might be the RTT, static content slow (might need expire tags), dynamic content slow, SSL handshake slow....
Post your results and more specific question and you might get more quality responses.
|
Posted by mixmox, 02-11-2015, 06:54 PM |
any special configuration you have for apache + modepagespeed?
|
Posted by mandrei99, 02-12-2015, 07:19 AM |
I'm more of an nginx guy. Gave up apache long time ago. What is your website, if you don't mind ?
|
Posted by mtrc, 02-12-2015, 07:48 AM |
As a general rule, caching will solve the issue, but network speed is very important. You have nothing to do if network is slow. If most of your visitors are from Europe, choose a server in Europe. If most of them are from USA choose a server in USA or Asia etc. The speed depends on server latency as well.
|
Posted by mandrei99, 02-12-2015, 08:11 AM |
Actually, there is. Have a look at http://www.cdnplanet.com/blog/tune-t...m-performance/
The problem is TCP protocol with high RTT times and more specifically because of the slow start mechanism in protocol. Increasing your servers TCP initial send window to 10 MSS basically your server starts sending 10TCP packets and waits for ACK. Instead of 2, wait for ack, 4, wait for ack, 8 wait for ack (basic example, it depends a lot on tcp implementation) where every wait is an RTT.
Also, you need to analyze your network if has loss, specifically if one upstream network device drops packets. Check intensivelly your network and report to the provider. If it does not, there are tweaks also for TLS, TCP depends on where the problem is (if any).
The ABC of website tuning is: SSD, database tuning, GZIP, mimify your scripts to squeeze a small size, image sprites, tcp tuning, tls tuning (decrease tls record size), memory buffers of the OS, of the web server, reduce context switches between kernel and user land daemons like nginx and so on.
Your question is very very generic. Don't expect detailed answers.
|
Add to Favourites Print this Article
Also Read