vBET and performance
vBET have lot of optimizations. Thanks that you can provide your content in 53 languages very fast.
Of course translations are not made magically and some resources are necessary to provide those. We have users with really big forums which successfully run vBET without any performance impact notice (http://www.vbenterprisetranslator.co...rformance.html).
Still in case if you want to use vBET in fastest possible way, below are some configuration hints for you. Please note that those describe the most optimal configurations for performance reasons - sometimes by cost of available features, so do not fallow it if you do not have performance issues.
- Make sure you are using last version of vBET. We are constantly improving performance.
- (Since 3.3.4) Turn on Use Full File Cache For Guests and make sure that it works (check does cache files are created - need to set appropriate file privileges)
- (Since 3.3.4) Set higher values for Full File Cache For Guests Time To Live and also for Full File Cache For Guests Time To Live For Les Relevant Pages
- (Since 3.3.4) Consider which pages can be hold longer in full file cache for guests and add those to Less Relevant Pages For Full File Cache For Guests
- vBET supports all encodings, but it is best if your forum uses utf-8 encoding, otherwise for each translation vBET have to re-encode whole page and do other additional tricks (also special characters takes much more place in DB cause those are changed to &#CODE; notation). If you are already running forum, there is no easy way to switch encoding (still it exists), but if you are creating new one then please consider to run it on utf-8 encoding which is designed to multilingual support.
- You can disable some translations at the begging - when cache will be filled you can add new ones from time to time. Starting with all 52 translations means 52 times more content for users and roots. Some forums can easily handle this, for some it is better to start with few translations.
- Make sure you have cache on.
- For later it will be important for you to have appropriate Cache TTL. Bigger is better, but not more that 15 days to be fair with Google TOS
- Choose best cache clearing strategy for your forum. For most forums 'Normal deletion' is best clearing strategy, but if you have really lot of translated content then normal cache deletion can kill your server. But be calm - we have special solutions for that cases. So you can choose 3 other strategies. Last one is fastest, but removes all cache content, so use it only if you have to.
- Use "Cache clearing timelap" - vBET clears over 150 cache tables removing lot of data. You can order vBET to wait between each table. Whole task will take same amount of resources, but your server will "rest" between clearings so server load will be smaller.
- Use option "Select grouped translations" according to your needs - this will make less queries to database so it will cost you less CPU, but by cost of more usage of RAM memory.
- Do not set "Stop looking after x failures" to low or too high. This option optimizes cache usage. Thanks that vBET will stop trying to find in cache translations which are not there. If you set it too high vBET will try more times. If you set it too low vBET can stop looking translations which are really in cache only because some small changes happen on translated page.
- Enable cache for all translations. vBET allows you to disable cache for chosen translations if you do not have too much space on disc, but such translations will take longer, since Google will be asked each time for those.
- Set "Google Language Detection" to "Always trust user". vBET have great feature which allows to detect real language of message in case if user mess up something. But it have its cost - additional ask to Google have to be made when new post arrives.
- Disable "Translate Google Maps". It allows you to translate Google maps included in your forum, but if you do not support those then disable it - it cost additional search and replace for links to Google map in whole output.
- Experiment with option "Don't translate usernames". It causes less asking for translation, by cost of many additional checks in many forum places. So there is something for something - check which is better in your case.
- Disable "Translate vBSEO messages in JavaScript" if you are not using this vBSEO functionality or disable it also in vBSEO. Translating it costs additional output parsing.
- Block robots for not relevant pages - like members pages, calendar and so on. Robots are able to visit every corner of your forum very fast - what can improve your CPU usage for first translations. Mostly forum doesn't need member pages be indexed, but still it will take your forum resources to translate those pages. So block robots for all not relevant pages in all translations. In next post you will find robots.txt example for that - this is part of robots.txt used by this forum (note that URL's are changed by vBSEO, and our forum uses subdirectory in URL).
- (Since 3.3.1) Using "Show original text" in booth versions - for users and guests. This options allows you to choose how you want to show original message. Showing it costs a little - it is not significant, but if you already done everything and seek for some little improvement then you can find it here. First of all - you have 2 ways to show original text if you wan: by JavaScript injection and in normal way. Normal one is better for performance, but injected one is better for SEO (robots do not see it). So if you feel you want show original content for booth - users and guests - then it is best to show injected for guest and normal for users. Of course you can choose to not show original text - it will be worst for your users but little better for performance. And you have also one more option - best for performance and worst for users - you can choose do not show original text or even message that it was translated. This option is best for performance because it is not using templates at all, worst for users, because they will not see that message was written in different language.
- If you have vBET integrated with vBSEO Sitemap Generator, then please check does it is in new way (much faster). Here is actual integration procedure: http://www.vbenterprisetranslator.co...tegration.html
- (Since 3.3.2) Play with advanced performance parameters: 'HTML size: cutting point' and 'HTML size: start cutting'. Please note that PHP performance drastically goes down when working on really big strings. I suppose that in such case PHP just writes it to some temporary file and is working on file instead of in memory. Because of that we modified translation algorithm and really big outputs are cut in smaller pieces during translation. This modification influences only large pages and you can configure it by mentioned performance parameters.
- (Since 3.3.2) Play with advanced performance parameter: 'Delay between translations'. On some forums if request to Google are send one by one immediately then responses comes from Google in longer times or even are blocked by forum server. DO NOT use it without any measurement of performance changes and do such only with cache off to see real impact.
- (Since 3.3.2) If you are using vBSEO please make sure that it is appropriately integrated. We made great improvements in integration between vBET and vBSEO which gives you better performance (no double redirects). So just go to integration section in readme.html file from vBET package and check described vBSEO files does those have appropriate changes.
- Set bigger Cache Lifespan for RSS channels (in vBulletin options). It defines how long once generated RSS XML will be valid. Another generation will be after this time. So bigger value means less actual data, but also better performance.
- (Since 3.3.4) Do not use option Don't translate code html tag if you do not really need to. Most forums do not allow users to put html code in posts, so it is not needed for most forums. Please note that content of code bbcode will not be translated anyway.
- (Since 3.3.5) Turn off option Translate 'alt' attributes. It has small impact on performance but still requires additional output parsing with regex and at least one more request to Google (if results are not cached). Because translated results are not visible in browsers (only when mouse cursor is over the image) it will have no impact on your users when turned off.
- (Since 3.4.0) Use Memory Cache. If you have your server configured to use Memory Cache, just go to admincp->vBET cache->Memory cache and choose the best option for you from Use memory cache. IMPORTANT: to use Memcache you need to put memcache host port!
- Change .htaccess rules.
NOTE: only if you are NOT using links with 2-signs part i.e: yourforum.com/XY/ etc.
Now you can use short rules!
Everywhere where you find
You can replace it withCode:(af|sq|ar|be|bg|ca|zh-CN|hr|cs|da|nl|en|et|tl|fi|fr|gl|de|el|iw|hi|hu|is|id|ga|it|ja|ko|lv|lt|mk|ms|mt|no|fa|pl|pt|ro|ru|sr|sk|sl|es|sw|sv|zh-TW|th|tr|uk|vi|cy|yi)
which will make your site work faster!Code:(..|zh-CN|zh-TW)
I.e. changing rules for user with intagrated vbseo:
into these:Code:RewriteRule ^/?(af|sq|ar|be|bg|ca|zh-CN|hr|cs|da|nl|en|et|tl|fi|fr|gl|de|el|iw|hi|hu|is|id|ga|it|ja|ko|lv|lt|mk|ms|mt|no|fa|pl|pt|ro|ru|sr|sk|sl|es|sw|sv|zh-TW|th|tr|uk|vi|cy|yi)/$ vbenterprisetranslator_seo.php?vbet_lang=$1&redirected=/ [L,QSA] RewriteRule ^/?(af|sq|ar|be|bg|ca|zh-CN|hr|cs|da|nl|en|et|tl|fi|fr|gl|de|el|iw|hi|hu|is|id|ga|it|ja|ko|lv|lt|mk|ms|mt|no|fa|pl|pt|ro|ru|sr|sk|sl|es|sw|sv|zh-TW|th|tr|uk|vi|cy|yi)/(.*)?$ vbenterprisetranslator_seo.php?vbet_lang=$1&redirected=/$2 [L,QSA]
NOTE: if your forum use subdirectory in URL, then change 2 first rules adding your forum directory with leading '/' just after redirected=. So i.e. if your forum is in forum directory then you will have redirected=/forum/index.php and redirected=/forum/$2Code:RewriteRule ^/?(..|zh-CN|zh-TW)/$ vbenterprisetranslator_seo.php?vbet_lang=$1&redirected=/ [L,QSA] RewriteRule ^/?(..|zh-CN|zh-TW)/(.*)?$ vbenterprisetranslator_seo.php?vbet_lang=$1&redirected=/$2 [L,QSA]
Since realases vBET 4.4.5 and vBET 3.5.3 you can find these rules into your download files:
do-not-upload\tools\redirecting-rules\short-redirecting-rules- (Since 3.6.2) Turn off option Don't translate numbers. You'll find this option in AdminCP -> vBET -> Translation Options. Has little effect on performance, but it still requires an additional parsing characters. Anyway it is not reccomended to turn if off, because it increases the cost of translation.
- Do not display the current date and time. Display the date and time causes additional translations every minute and additional queries to the database even if the data is already in cache.
In order not to display the current date and time:
From now on, the current date and time will not be displayed.
- Go to AdminCP->Styles & Templates->Search in templates
- Search:
Code:$vbphrase[all_times_are_gmt_x_time_now_is_y]- Remove it from all the templates.
Please note that other templates can display the time by other variables - in this case, you need to find the variable and remove/comment it.- Do not show any rotating text on page. Rotating text makes that vBET sends more text to be translated.
If you want to put on page rotating text put it in JavaScript (text in JavaScript is not translated) or in notranslate area.- (Since 3.6.3) Turn off option Add alternate tag. Enabling this option increases overhead time to add the tags and sends more data to users. By default, this option is disabled.
Automatic Translations (Powered by Google, Microsoft®, Yandex, SDL Language Cloud, IBM Watson and Apertium):
- What's New?
- Forum
-
Translations
