Does it still happens when you disabled scheduled task "vB Enterprise Translator (Cache TTL)". How big are your cache tables? When server fall happens do you have any errors in log files? Did you try to use vBET parameter "Cache clearing timelap"? What clearing strategy are you using right now?
You didn't answer most important information - does it still crashes when scheduled task is disabled? First we need to determine does vBET is real issue here.
In normal deletion old cache is deleted daily. If you want fastest way of deletion - use last strategy - this one will remove whole cache once per 15 days. It works immediate and use practically 0 server resources. But you have to fill whole cache again, not just old one.
Did you tried to use "Cache clearing timelap" option?
Cache clearing timelap
How many seconds to wait between clearing cache tables. Set 0 to disable. Please note that vBET has over 150 cache tables to clear - setting this value too high may cause that clearing which starts at night will continue even in day hours. Also please do not set it higher that your MySQL connection is waiting without usage (mysql setting: wait_timeout) - otherwise it will cause 'MySQL server has gone away error' and clearing will not be finished.
Sorry - I don't get one thing - you have clearing twice a day? Please disable clearing task and tell does your server will crash when clearing is disabled (no matter at which hour - disable it completely). If server will not crash when cache clearing is disabled then it means that vBET is guilty. If still crasches then something else causes this.
If vBET is guilty then you have several options to tune it up:
- set bigger value to "Cache clearing timelap" - this will give time and more CPU for other threads between clearing each cache table. I suggest to do this in first place
- Set lower "Cache Time To Live (TTL)" - then your tables will be smaller so clearing will be less expensive.
- Play with "Cache clearing strategy" - the last one will solve your issue in 100% - it is designed for very large cache and will clear even huge cache immediately, because it just removes whole cache tables and creates it again. But it clears whole cache once per Cache TTL period, so cache have to be filled from beginning. This is last thing I advise to use, so if nothing else is working this will in 100%. It is added just for such situations![]()