What kind of environment are you running your laravel app on? If it's vagrant it may in some cases run very slow compared to a vps or something similar.

ehm, I just use MAMP on Mac OS to create my localhost server

I've had similar issues. Hoping someone has insight on reducing boot time

Laravel 4.2 on Homestead on Windows 8.1 (HDD) with Shared Folder

Laravel 4.2 on Homestead (v0.2.0 HHVM) on Windows 8.1 (HDD) - SFTP (via PHPStorm)

What exactly is homestead? I know it's some virtual server but how do you use it?

I usually just use MAMP.

And the loading time is incredibly different between shared folders and SFTP. That's strange

Homestead is a customized vagrant box for Laravel development. http://laravel.com/docs/4.2/homestead

That is just on my local machine. I bet running it on a production server with SSD would be even better.

So it's an alternative to something like MAMP or XAMPP?

We devs generally develop on a Mac or a Windows machine for a production environment running linux. This creates a lot of compatibility issues and born is the infamous "works-on-my-machine" codebase.

So, using vagrant we just solve that problem. Its a virtual machine running linux on your dev workstation. It mimics your production server. Homestead is just a easy to start copy for laravel devs and mimics the env provided by forge provisioned servers.

Unrelated question, but how do you manage to have that debug bar ?

Ah okay. That sounds nice :) Would it be difficult to change the environment to run on other servers?

@cheskq https://github.com/barryvdh/laravel-debugbar

By environment I wasn't refering to the app_envoronment. Its the os, apps and the environment your app runs on.

Just an example. I develop on windows. There is no easy way to get memcached or beanstalk running on windows so homestead helps me that way.

+1 to mcraz ditch mamp or local development and devlop on a VM that will mirror your prod environment

cheskq said:

Unrelated question, but how do you manage to have that debug bar ?

"barryvdh/laravel-debugbar": "1.*"

I used to have issues with my dev machine going slow when using MAMP. However, I've recently switched to Vagrant and they've gone now. The initial 'WTF is Vagrant? Something else new for me to learn!' fear disappeared once I started reading about it, and watching the videos on Laracasts. If you're not a member, you should join up. Here's a list of vagrant videos. There's a couple of free ones to watch too.

https://laracasts.com/search?q=vagrant

Okay thank you guys. I think I will switch vor homestead.

The problem is that I don't know what server I will run my application on yet.

If you have the freedom of choice go for a forge provisioned server after developing on homestead.

It does state the follow note on the debugbar read me;

https://github.com/barryvdh/laravel-debugbar

Note: Use the DebugBar only in development. It can slow the application down (because it has to gather data). So when experiencing slowness, try disabling some of the collectors.

Maybe this is the issue?

@mcraz Hm, It looks pretty expensive :/

@WayneHarris I removed the debug bar before I tested the speed. It changed nothing though.

One of the reasons why its slow, is the rendering process. depending on how much repeated nested views u have, it might causes big performance drop based on a profiling i've done lately.

To be able to make something good out of it, try this. https://github.com/Te-cho/compile-blades

can you help me? links: https://laravel.io/forum/laravel54-eloquent-orm-use-toarray-error