Cleaning up the X-cart cache<\/p>\n
By default (?), the cache is at \/var\/www\/html\/cache or [DOCTUMENT_ROOT]\/cache. If there are too many files, you will not be able to delete the files. The following commands can help.<\/p>\n
The permanant fix for this X-cart behaviour is to change the following row in the config.php file from:<\/p>\n MySQL<\/strong><\/p>\n There are tons of issues like a db that is not upgraded, joins without indexes etc. We decided to make use of the RAM & have MySQL MYISAM temporary files in there for faster access. Don’t forget to create the required directory and add the necessary entries \/etc\/fstab to persist the changes over reboots.<\/p>\n \/etc\/my.cnf is changed as follows<\/p>\n Now that we have some room to look into other matters, things should be easier.<\/p>\n We also had the non-so-friendly max connections error. We increased in the max connections from the default.<\/p>\n Slow Queries<\/strong><\/p>\n If the slow query log is enabled, mysqldumpslow can be a very handy command<\/p>\n Reading mysql slow query log from \/var\/log\/mysql\/slow.log Count: 376687 Time=1.63s (613441s) Lock=0.00s (36s) Rows=203657.1 (76714970948), 2users@localhost SELECT productid, COUNT(remote_ip) AS total, AVG(vote_value) AS rating FROM xcart_product_votes GROUP BY productid<\/em><\/p>\n Controlling the RAM usage<\/p>\n <\/p>\n The RAM usage on GNU\/Linux based systems can be sometimes quite weird. The immediate path taken is to play around with sysctl and tweak swappiness<\/a>\u00a0& may be run drop_cache.<\/p>\n ie,<\/p>\n change swappiness<\/em> to say, 10 & do a cache + buffer cleanup<\/a>. But these may not be very handy but the\u00a0\/proc\/sys\/vm\/vfs_cache_pressure <\/strong><\/a>changes seems to help further. (we have it around 512)<\/p>\n Further minimum free memory size is a parameter which can help preventing OOM errors. A sample value is shown below.<\/p>\n Further:<\/p>\n <\/p>\n Keep an eye on Caches and Buffers<\/strong><\/p>\n This is often something people miss. \u00a0 The difference between free command and the total process usage can give us the Cache + buffer usage. \u00a0slabtop is a very handy command to get exact details.<\/p>\n <\/p>\n Another very useful tool is dstat<\/strong><\/p>\n dstat -lrvn 10 output is shown below. This can give colourful details of cache usage.<\/p>\n the memory, CPU, network, IO columns above gives useful information.<\/p><\/div>\n <\/p>\n
\ntouch \/root\/agileblaze\/cache-file-list.txt #empty file
\nfind . -name '.js' | grep -vFf \/root\/agileblaze\/cache-file-list.txt | xargs \/bin\/rm -f
\nfind . -name 'sql.<\/em>' | grep -vFf \/root\/agileblaze\/cache-file-list.txt | xargs \/bin\/rm -f
\nfind . -name 'rf*.php' | grep -vFf \/root\/agileblaze\/cache-file-list.txt | xargs \/bin\/rm -f
\n<\/code>
\n<\/em><\/p>\ndefine('USE_SQL_DATA_CACHE', true);
\nto
\ndefine('USE_SQL_DATA_CACHE', false);<\/code><\/p>\ntmpdir = \/var\/mysqltmp # changed from \/var\/lib\/mysql\/tmp<\/code><\/p>\n# MAX CONNECTIONS
\nmax_connections = 300 #Sat Apr 30 03:35:25 CDT 2016<\/code><\/p>\n[root@714219-db1 mysql]# mysqldumpslow -a -s r -t 10 \/var\/log\/mysql\/slow.log <\/em><\/code><\/p>\nsysctl -w vm.min_free_kbytes=2621440<\/code><\/p>\nsysctl -w vm.vfs_cache_pressure=1024
\nsysctl -w vm.swappiness=10<\/code><\/p>\nslabtop --delay=10 -s c<\/em>
\n<\/code>
\nCan give a neat summary.<\/p>\n![\"Screenshot](\"http:\/\/www.migrate2cloud.com\/blog\/wp-content\/uploads\/2016\/05\/Screenshot-from-2016-05-11-20-28-07-300x285.png\")
<\/a><\/p>\n![](\"https:\/\/www.migrate2cloud.com\/blog\/wp-content\/uploads\/2016\/05\/2017-02-20_19-30-30.png\")
<\/a>