UMI 2.7.4.

Quote from the documentation:

When testing, UMI.CMS withstood more than a million requests per day on a simple uniprocessor server P4-1600 1G RAM, while working in parallel with dozens of other sites.

But my brakes. The server thinks about 4 seconds, and only then begins to give content.

Here is a test

Iron:

  • Intel Atom CPU D2550 @ 1.86GHz - 2c / 4t
  • 2x2GB DDR3 1066 MHz
  • HDD: 2 TB
  • Apache 2 in mod_php mode
  • PHP 5.5.9
  • MySQL 5.5.43

Worth gzip and all modules that are listed in the documentation.

It can be said that the server is idle ( load average ~ 0.25) and there are about 20 visitors per day on the site under test.

From the jambs:

You cannot turn on the accelerator (I tried memcache and apc ), because from the previous programmer I got a curved DB division system for one admin panel, so the templates start getting confused.

And does not want to enable static caching, i.e. put a tick, save → tick disappeared.

The plans for the front put nginx , but I do not think that it will save the situation.

  • solve the problem of caching - and you will be "a million requests per day." well, at least, not all pages will be generated with each conversion, as is happening now. - aleksandr barakin pm
  • Now there are no requests at all, but such a delay. Here is another problem. - Sergey Horoshev
  • how not? you yourself write: make a request to the site. and in four seconds you get the answer. for a complex and overloaded with framework, which is umi, it seems to me that this is quite normal. but subsequent requests to the site should take part of the already cached information and run much faster. but your caching is disabled. and therefore each request to the site is carried out "from scratch". - aleksandr barakin
  • but partly you are right: it is likely that there are still some problems that contribute to the overall response time. but I would, faced with a similar situation, first of all set up the work of php-caching. and then I was looking for other culprits. - aleksandr barakin
  • Unfortunately, I will be setting up caching last, because the previous programmer rewrote the multisite in his own way. He apparently did not even suspect that it was necessary to fully test his decision first. I agree with you, but now the server is completely idle and given away by the UMI, and as a result we have such disgusting performance. - Sergey Horoshev

1 answer 1

Cannot enable accelerator (tried memcache and apc)

but it would be necessary.

without information caching, the interpreter with each request, executing the php -site code, initializes megabytes of information again and again.

the time of this initialization is most likely the lion’s share of those very “four seconds of reflection”.

but, quite possibly, there are other "unproductive" delays, which, it seems to me, should be dealt with after eliminating the cause of the main delay.