robert syputa
New Member
One trick to improve performance by a couple percent is to edit the php.ini file or, if available to you, a custom PHP config file to include a line as suggested by the ioncube installation manual as follows (for alidropshipwoo plugin - modify for different directory name for non-woocommerce plugin):
ioncube.loader.encoded_paths = "/home/nginx/domains/yourdomain.com/public/wp-content/plugins/alidswoo/"
(change path above to fit your server host)
Ioncube reads the php.ini and custom config files. If that line is included, it will only read the file headers in the alidswoo plugin file folder instead of all of the files on the server site. Since the alidropship plugin is only used in the backend/admin processes, the customer-facing website will not be slowed down by the unnecessary reading of headers.
The ioncube loader is efficient in that it reads headers and does not process pages not encoded for ioncube. However, as a default, it does not know which directories hold encoded files, so it reads all of the files. That adds 2-4% of process overhead, not a lot but every bit matters.
ioncube.loader.encoded_paths = "/home/nginx/domains/yourdomain.com/public/wp-content/plugins/alidswoo/"
(change path above to fit your server host)
Ioncube reads the php.ini and custom config files. If that line is included, it will only read the file headers in the alidswoo plugin file folder instead of all of the files on the server site. Since the alidropship plugin is only used in the backend/admin processes, the customer-facing website will not be slowed down by the unnecessary reading of headers.
The ioncube loader is efficient in that it reads headers and does not process pages not encoded for ioncube. However, as a default, it does not know which directories hold encoded files, so it reads all of the files. That adds 2-4% of process overhead, not a lot but every bit matters.