In the main configuration, you will find the main options as well as some other button to access various sections of the configuration
Here’s the main option described with more details:
This options allows the module to collect the html of a page and save it to a file.
Then when the same page is requested it, the module read the file and serves it directly instead of executing the whole page PHP again.
This method will lead to a faster load of the page. You can enable memcache in the Performance page so that the module serves the cached html even faster.
Of course, the module checks that the served html is up to date by checking which tables the page uses and if a table has been changed.
If a change is detected, the module will allow the PHP code to execute again and the saved page html will be refreshed based on the response.
To disable the database check, you can disable the option “Validate database tables” (not recommended)
If this option is enabled, the module will check if a database table that the request uses has been changed since the last caching of the page html.
The module will cache module templates and if the same template variables are assigned, it will load the template response from cache instead of letting PHP execute it.
Same as caching module templates. It will make template themes load faster if they are already cached.
To prevent the module tables from getting large, the module will delete old cache data when it’s older than one month, one week or one day based on your preferences.
If your shop has large traffic and a great number of visits, you may want to pick the option “one week” or even “one day” for extreme cases