Please note that we have already planned supporting of other cache systems and our translation algorithms are instantly optimized. I.e. we just discovered how drastically decreases PHP performance when working on large strings and we modified our algorithm. It is already released in vBET 4.2.0 with additional configuration options. And we will move all improvements also to vBET 3.x which is still supported
...
Our devise is: "We have lot to change". And that is why we are experimenting, changing algorithms, profiling and spend lot of time looking for solutions which will require less resources. Still we know no mod which could be any competition to vBET and there are some other translation mods. We made lot of algorithm changes which we had to trow away because they didn't help, during this process we also discovered many improvements. You can have your impression basing on your server issues, but please consider do you have any better solution? What could you give a hint that maybe vBET is not wrong solution since is working on thousands of forums, maybe you are just trying to put 20 liters of water into 10 liters bucket. Still - we have lot to change and great TODO list in optimization section (about 70% to experiment will it help or not)
And you are 100% right - we can do it better, we will and we ARE doing it all the time
Just wait till we move all improvements which we made during vBET4.x implementation
If I can give you some hints - please check how you can optimize vBET:
http://www.vbenterprisetranslator.co...rformance.html
Especially consider disabling some languages and blocking irrelevant pages by robots.txt