Inquiry Regarding Foundation SaaS Starter Kit Release

Well that smells like good news, looking forward to it.

@bobbyiliev, I did a tryout of the current release of wave 3, but it was too slow, like way too slow, and I thought my pc was lagging or something so I decided to have a live deployment and see if that was the case but unfortunately even on a live server it's too slow, here's my deployment wave 3.

server specs RAM: 8Gb Processor: 6 Cores Nothing else's on the server and half resources are allocated to PHP

Hey!

Hm this is quite interesting! It sounds like might be a certain configuration setup that is causing the problem.

Is there any chance you could give me access to that server so I can look into it? No worries if not, it would be helpful if you could share the exact server configurations that you have and the wave config as well and I can try to reproduce this on my end!

- Bobby

Hey!

Thank you for sharing the login details!

What I've noticed so far is:

• The slow response time is the main reason why the site is slow, it takes about 4 seconds for the server to do the initial response:

• After running php artisan optimize this dropps to around ~500ms:

Further looking into the server it looks like that your server uses HDD rather than SSD disks:

# lsblk -o NAME,ROTA
NAME   ROTA
sda       1
├─sda1    1
├─sda2    1
└─sda3    1

# cat /sys/block/sd*/queue/rotational
1

Since your server is using an HDD, this could be causing the slower initial load times without running php artisan optimize. HDDs are slower at reading and writing data compared to SSDs, especially when loading uncached configurations, routes, and views. Laravel's optimize command caches these resources, reducing the need for frequent disk access and significantly improving performance.

Upgrading to an SSD would allow faster data access, potentially minimizing the load time even without optimize.

well noted, I can see a huge improvement

Thanks.