.env performance

I am wondering if anyone has tested the performance implications of using .env in Production environments. Their documentation advices against it:

phpdotenv is made for development environments, and generally should not be used in production. In production, the actual environment variables should be set so that there is no overhead of loading the .env file on each request. This can be achieved via an automated deployment process with tools like Vagrant, chef, or Puppet, or can be set manually with cloud hosts like Pagodabox and Heroku.

WordPress loads like 1k+ files on a typical request.

Seems like a waste of time to actually test the performance difference, but Iā€™m sure someone out there has.

1 Like