Slow page load in my basic web app about puphpet

[frastel]

This may be the problem of the shared folder and not of the box itself. Mounting the folder with NFS solves the problem but this is not possible on windows hosts. Big projects should not be loaded within the shared folder. Install the project in another folder directly in the box (e.g /var/www/myproject if /vagrant is your shared folder) and let apache point to this folder. Page performance should be noticeable increase.

[jtreminio]

This may also be due to Xdebug being enabled in session and expecting a connection to be made.

Maybe we can do something about that...

[Surreal9]

Ah, thanks for the info. It did turn out to be a result from xdebug, I believe the setting "xdebug.remote_autostart" specifically, from etc/php5/apache2/php.ini

Once I set that to 0, things started working. I also notice that the 'in-vm' phpmyadmin code does run about 40% quicker vs my shared-folder code, so frastel I see what you mean.

[Surreal9]

Well, this issue for me is solved since I know how to fix it in the resulting VM, but I guess ultimately it's still a potential issue in the code, where I'm not terribly sure how to fix it.

[frastel]

@jtreminio We should deactivate xdebug.remote_autostart by default. Newbies will be getting very confused when this mode is enabled and they will not know why the page is so slow.
I accidentally enabled it during my latest tests and it is really incredible slow when you are not prepared for it :)

[Surreal9]

I noticed the Puphpet web page says remote_autostart should be set to 0 by default, but when I download a new manifest /etc/php5/apache2/php.ini still has it turned on by default.

[Surt]

yes, remote_autostart is still turned on by default.
I had problems and, as a newbie, I had to search for information until I reach this post.