A
A
Artyom Pinul2018-03-05 18:52:00
Nginx
Artyom Pinul, 2018-03-05 18:52:00

How to reduce centos + VestaCP server response time?

Good afternoon.
We have our own laptop-based server.
Server specifications:
- CPU AMD Athlon II P360 AMP360SGR22GM 2.3 GHz
- 120Gb SSD
- 4Gb RAM
- OS --> Windows server 2012 --> Hyper V --> Centos 7.2 (for which 2 GB is allocated RAM and 2 CPU cores).
On a virtual machine based on CentOS 7.2 + VestaCP control panel (running in conjunction with Nginx + phpfpm), I have a website running on the OcStore engine. Which, when tested by the cy-pr.com service, gives me a message about the need to reduce the server response time. It takes no more than 0.2 seconds, and I have 1.5 seconds.
How can I reduce the server response time to an acceptable one? What can be recommendations? Thanks in advance.

Answer the question

In order to leave comments, you need to log in

2 answer(s)
B
Boris Syomov, 2018-03-05
@kotomyava

Put the site on a normal hosting.
You have everything done to ensure that everything is very slow:

  • Old, slow processor.
  • A laptop where everything is designed to reduce power consumption, and not for speed.
  • Virtualization, which gives additional overhead.
  • All this is still, I suppose, on the home Internet, with an unknown quality of the outgoing channel and unpredictable delays ...
  • To the heap, I suppose, no one set up the same mysql, for example. And in general, no one set up anything - the socket is installed and ok, but in fact, the socket is not needed here at all.

V
Vladimir Skibin, 2018-03-05
@megafax

See all timings:
1. DNS query time - usually no more than 10ms
2. Request time - no more than 50ms
3. CMS page generation time on the server - this time should not exceed 2s. It just depends on the processor capacity of the server + the capabilities of the CMS itself + the configured caching in the CMS itself
4. the time of delivery of the primary content to the browser. for a stationary it's no more than 500ms, for mobile - no more than 1.5s
5. rendering time of this primary content (HTML) by the browser, the time is similar to n4. the weaker the machine with the browser - the slower
6. the time of requests and delivery of auxiliary scripts / pictures - this is the final render / execution - no more than 5s
I use these timings mainly to explain "work speed" for "managers".
Of course, they can all be reduced.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question