vBET
28-03-10, 11:19
Hi :)
If previous versions was fast this one have light speed ;) Seriously - we discovered and get rid of few bottlenecks. So this version will translate even faster and with much less server load :)
IMPORTANT FOR vBSEO users: additional integration step is required during update. It will remove double redirects and save lot of your server resources. For details go to readme.html file and find part about header ("Location: $fulluri");
What changed in this version:
Performance improvments:
- Eliminated bottleneck for URL translation.
We realized that links was translated one by one what cost lot of Google requests. Now vBET uses delayed translation for URL translation. In case of vB Friendly URLs it works for all not canonical URLs. In case of vBSEO URLs first 4 links must be translated at demand (because of possible redirects) and rest is delayed.
- Eliminated bottleneck with vBSEO redirects.
Double redirects are no longer used - now redirect to translated link points on appropriate link at first redirect (additional integration step required).
- Plugins body moved to php file.
Now large text blocks will no loner be taken from database. Instead of this plugins simply use functions which are in php file. Most of plugins have 1-4 lines of code now.
- New advanced performance parameter 'Delay between translations'.
We discovered that some forums have issue with lot of Google requests (note - only some, most do not have such issue). It appears for those forums that each another Google request took longer and longer. Maybe because of Google 'punishments' for lot of traffic, maybe because it's own firewall settings. Anyway we have solution for that - now you can ask vBET to wait between Google translation requests. Of course it makes user request evaluation longer on your side, but it appears that in those cases final response is much, much faster. Because for not cached page waiting for Google response takes most time. Use it carefully and only if you can measure performance changes. If it will be necessary we will add some article about how to check Google response times.
- Bottleneck with text replacements eliminated.
We profiled vBET and found performance issue with output parsing - now it is corrected. Output parsing for scripts, styles, not translated areas and translation tracking is much faster right now.
Templates changed:
- vbenterprisetranslator_flags
Bugs corrected:
- HTML validation errors corrected
- base tag on forum main page with vBSEO working OK now
- Redirecting with vBSEO links corrected
Have fun and enjoy much waster translations, with much less server load :)
For vBET3.x users - we are going to move those performance improvements to vBET3.x right now. So you will also enjoy much faster solution :)
If previous versions was fast this one have light speed ;) Seriously - we discovered and get rid of few bottlenecks. So this version will translate even faster and with much less server load :)
IMPORTANT FOR vBSEO users: additional integration step is required during update. It will remove double redirects and save lot of your server resources. For details go to readme.html file and find part about header ("Location: $fulluri");
What changed in this version:
Performance improvments:
- Eliminated bottleneck for URL translation.
We realized that links was translated one by one what cost lot of Google requests. Now vBET uses delayed translation for URL translation. In case of vB Friendly URLs it works for all not canonical URLs. In case of vBSEO URLs first 4 links must be translated at demand (because of possible redirects) and rest is delayed.
- Eliminated bottleneck with vBSEO redirects.
Double redirects are no longer used - now redirect to translated link points on appropriate link at first redirect (additional integration step required).
- Plugins body moved to php file.
Now large text blocks will no loner be taken from database. Instead of this plugins simply use functions which are in php file. Most of plugins have 1-4 lines of code now.
- New advanced performance parameter 'Delay between translations'.
We discovered that some forums have issue with lot of Google requests (note - only some, most do not have such issue). It appears for those forums that each another Google request took longer and longer. Maybe because of Google 'punishments' for lot of traffic, maybe because it's own firewall settings. Anyway we have solution for that - now you can ask vBET to wait between Google translation requests. Of course it makes user request evaluation longer on your side, but it appears that in those cases final response is much, much faster. Because for not cached page waiting for Google response takes most time. Use it carefully and only if you can measure performance changes. If it will be necessary we will add some article about how to check Google response times.
- Bottleneck with text replacements eliminated.
We profiled vBET and found performance issue with output parsing - now it is corrected. Output parsing for scripts, styles, not translated areas and translation tracking is much faster right now.
Templates changed:
- vbenterprisetranslator_flags
Bugs corrected:
- HTML validation errors corrected
- base tag on forum main page with vBSEO working OK now
- Redirecting with vBSEO links corrected
Have fun and enjoy much waster translations, with much less server load :)
For vBET3.x users - we are going to move those performance improvements to vBET3.x right now. So you will also enjoy much faster solution :)