Docket Cache Folder and NGINX.

Ok, here you’re little wrong.
First, the problem is not in the front.
Problems start to overload the server in the backend when you edit pages, for example:
try edit 10 pages in the same time, server get overload.

For the record, when i turn off your plugin, i can easily edit 10 pages in the same time.

And the must important:
cache enabler cache only pages on the front, not admin sections.

Your plug in is the only plugin to cache admin objects.
When you turn off your plugin, you can edit 10 pages in one time.

Now, i use cPanel with Engintron (NGINX Plugin design for cPanel)

Nginx caches this folder.
In dynamic and in static cache, nginx produce.

You try run -cUrl you will see response come from NGINX.

The overload is because NGINX utilize the backend, make cache for the backend, because of this folder.

If you not believe me:
https://github.com/engintron/engintron/tree/master/nginx

get inside proxy_params_static
and
proxy_params_dynamic,
you will understand these folders actually get read by
Nginx (Engintron)

Not only Engintron, any NGINX on Fast CGI read these folders…
It is no matter, NGINX / ENGINTRON read all the folder and create another cache of your plugin.
Inside NGINX.

ANY NGINX, NOT ONLY ENGINTRON.

If you can look on what i sent you,
you can see Engintron inside the Dynamic cache, excluded any possible PHP.

If you be able to excluded nginx via php string, the engintron will not cache the admin backend. (generally better excluded nginx from php, php is heavy)

It will be better,
look on what i send you.
By the way: cPanel + Engintron is the must clients in the world use it (70% use cPanel and 40% from this use Engintron as Nginx.)

Now as i said, i can do it by my self throw Engintron,
but i prefer to keep everything default.
Why?

This because have updates. And any update, something change.
It’s better if your plugin will support it by default.

I tell you that because your plugin is amazing, but still the plugin must
improvement and he will be a PERFECT, like AO and Cache enabler.

Now important thing, is the plugin actually helping to the server when you NOT EDIT
or work in the backend.

Problem accrue when you want to work on several pages in one time,

i will wait for the fix, hope this update will come soon, i turn off the plugin for now.