I have a client using this extension, and we recently discovered a big performance issue.
Description: The query generated by the \Amasty\Fpc\Model\ResourceModel\Activity::matchUrl
method runs a query on a table that is missing an index.
Here is a screenshot showing the slow query:
Once the client added a MySQL index for the table, the slow query went away:
I'd recommend adding an index to the amasty_fpc_activity table for a combination of the url
and mobile
columns. Something like this:
ALTER TABLE `amasty_fpc_activity` ADD INDEX `URL_MOBILE` (`url`, `mobile`);
Just don't use activity log and you will be fine.