I suggest you ...

Use nginx for php-fpm dynamic content - instead of the current setup of nginx reverse proxy for static and apache for php-fpm

The current setup seems to be only using nginx as reverse proxy in front of apache/php-fpm.

Right now requests seem to go this way nginx->apache->php-fpm.

We'd like to test with apache completely removed and nginx->php-fpm direct.

We'd like to have a nginx -> php-fpm setup for generating dynamic content on uncached pages for faster performance.

We are able to get twice the page loading speed from a direct setup on Linode with identical specs with Nginx used for php-fpm than the Thunderstack use of Nginx only as a reverse proxy and Apache for php-fpm dynamic content.

When a customer is logged-in to an ecommerce site much more of the content is served dynamically and cannot be cached - so all the caching in the world can only give performance to the static content.

Whereas, using Nginx & php-fpm for the dynamic content generation will give much needed additional performance for the dynamic conten webserver.

Out tests also showed no regressions in functionality with WP/Woo . and 160+ plugins.

24 votes
Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)

We’ll send you updates on this idea

Marcus Quinn shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

5 comments

Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
Submitting...

Feedback and Knowledge Base