Closed robbykrlos closed 3 years ago
We have never encountered problems with Enso's performance.
We're using (as min config):
You should get with that config < 35 ms per request (w/o heavy db activity).
On the demo server we have 4 cores i7-8700 and 50 gb ssd.
Note that we provision & manage all of our servers with forge.laravel.com, one of the best decisions we ever made. And deploy with envoyer.
recommendation from @dorincarsin who is our sysadmin.
https://www.hetzner.com/cloud -> go for the one that is 5.68 monthly.
Hi, Thank you so much for your inside info. That will definitely help! Thanks @aocneanu, @dorincarsin
For everyone else having performance problems with Laravel Enso - out of the box configuration - a huge performance boost will be by using Redis caching, instead of "file" as it comes by default:
CACHE_DRIVER=file
To:
CACHE_DRIVER=redis
Of course this does not work by just changing the configuration, you'll need to install Redis and php_redis extension for your environment.
For a low traffic and limited usage, Apache is still OK. nginx is faster but at this scale the performance improvements are very light.
This is a question.
Hi,
Are you guys willing to share your https://www.laravel-enso.com/ environment configuration?
I mean here:
I'm doing some research on the best performance we can get our of an Enso based application, and it seems that your demo test is quite fast compared to our test env. We have a RH7. No caching httpd2.4, php-fpm.
We have this initial "slowness" where if you don't login for 24h, the first login is very slow, and unresponsive. and even more the second action you try (ex, changing the menu will wait for ~4-5 seconds without anything changing).
After a while, things move faster, and actions are instant.
My feeling, after some performance profiling is that something on UI - loading js files. is slow. Because the API calls and DB results are usually fast. This is still WIP
Thank you,