This script is only limited by what Google Translation offers. At this point it is 28 languages. As for "Brazilian", I am not sure what part of Brazil speaks Brazilian, but in most of Brazil they speak Portuguese, which Google translation already offers....
Alter table wt_cache_short collate utf8_bin; ALTER TABLE wt_cache_short CHANGE tl tl VARCHAR( 10 ) CHARACTER SET utf8 COLLATE utf8_bin NULL DEFAULT NULL; ALTER TABLE wt_cache_short CHANGE originaltext originaltext VARCHAR( 50 ) CHARACTER SET utf8 COLLATE utf8_bin NULL DEFAULT NULL; ALTER TABLE wt_cache_short CHANGE translated translated VARCHAR( 255 ) CHARACTER SET utf8 COLLATE utf8_bin NULL DEFAULT NULL; Alter table wt_cache_medium collate utf8_bin; ALTER TABLE wt_cache_medium CHANGE tl tl VARCHAR( 10 ) CHARACTER SET utf8 COLLATE utf8_bin NULL DEFAULT NULL; ALTER TABLE wt_cache_medium CHANGE originaltext originaltext VARCHAR( 255 ) CHARACTER SET utf8 COLLATE utf8_bin NULL DEFAULT NULL; ALTER TABLE wt_cache_medium CHANGE translated translated VARCHAR( 1000 ) CHARACTER SET utf8 COLLATE utf8_bin NULL DEFAULT NULL; Alter table wt_cache collate utf8_bin; ALTER TABLE wt_cache CHANGE tl tl VARCHAR( 10 ) CHARACTER SET utf8 COLLATE utf8_bin NULL DEFAULT NULL; ALTER TABLE wt_cache CHANGE translated translated TEXT CHARACTER SET utf8 COLLATE utf8_bin NULL DEFAULT NULL; ALTER TABLE wt_cache CHANGE translated translated VARCHAR( 65000 ) CHARACTER SET utf8 COLLATE utf8_bin NULL DEFAULT NULL; CREATE TABLE saver ( id INT, tl VARCHAR(10), originaltext VARCHAR(65000) ) ENGINE = MYISAM, CHARACTER SET utf8 COLLATE utf8_general_ci; CREATE TABLE cleaner ( id INT ) ENGINE = MYISAM, CHARACTER SET utf8 COLLATE utf8_general_ci; delete from cleaner; delete from saver; insert into saver (SELECT min(id) as id, tl, originaltext from wt_cache group by originaltext,tl having count(*) > 1); insert into cleaner (SELECT cache.id from saver, wt_cache cache where saver.originaltext=cache.originaltext and saver.tl=cache.tl and saver.id<>cache.id); DELETE FROM wt_cache USING wt_cache INNER JOIN cleaner ON wt_cache.id = cleaner.id; delete from cleaner; delete from saver; insert into saver (SELECT min(id) as id, tl, originaltext from wt_cache_short group by originaltext,tl having count(*) > 1); insert into cleaner (SELECT cache.id from saver, wt_cache_short cache where saver.originaltext=cache.originaltext and saver.tl=cache.tl and saver.id<>cache.id); DELETE FROM wt_cache_short USING wt_cache_short INNER JOIN cleaner ON wt_cache_short.id = cleaner.id; delete from cleaner; delete from saver; insert into saver (SELECT min(id) as id, tl, originaltext from wt_cache_medium group by originaltext,tl having count(*) > 1); insert into cleaner (SELECT cache.id from saver, wt_cache_medium cache where saver.originaltext=cache.originaltext and saver.tl=cache.tl and saver.id<>cache.id); DELETE FROM wt_cache_medium USING wt_cache_medium INNER JOIN cleaner ON wt_cache_medium.id = cleaner.id; OPTIMIZE TABLE wt_cache, wt_cache_medium, wt_cache_short; alter table wt_cache_short drop index originaltext; create UNIQUE INDEX originaltext on wt_cache_short (originaltext, tl); alter table wt_cache_medium drop index originaltext; create UNIQUE INDEX originaltext on wt_cache_medium (originaltext, tl);
In addition, I have a lot of experience tuning MySQL for our site, and can see numerous issues in the database performance before and after mods are installed. For example, a mod that uses blobs in the MySQL db table cannot be tmp cached to memory and must be tmp cached to disk, lowering performance .... etc etc.
One of the things I noticed was that this mod uses blobs in the dB. After installing, my MySQL tuning scripts starting complaining that a high percentage of temporary tables were being written to disk v. memory. I doubled the size of both the heap and tmp table cache and it did not help giving the message (attached in the screen shot).
Note: I just rebooted MySQL, so the number of temp tables written to disk increases the longer this mod runs.
Cheers.
It does use blobs and it have to Any other solution for storing really long strings?...
My opinion is - silkroad is telling us what we use - I made it so I know what we use
Let him try to find out better solution if he thinks that it's possible
@silkroad - do you have any suggestions for better solution or just like to talk?...
PS: I have not drawn any conclusions, I just was commenting that I have noticed some differences in performance (before/after), so please don't be unhappy with me. Thanks.
As I already wrote - translated page will always generate slower, because first normal page is generated and then it is translated. So to normal time you have to add translation time which is greater than 0 - even if cached (time of taking translation from cache is also greater than 0) I'm suprised that you expected somesthing else
Thanks for your note - we are aware of this
Also note that mod don't affect time of normal page generation, because it does nothing then
As I already wrote - translated page will always generate slower, because first normal page is generated and then it is translated. So to normal time you have to add translation time which is greater than 0 - even if cached (time of taking translation from cache is also greater than 0) I'm suprised that you expected somesthing else
Thanks for your note - we are aware of this
Also note that mod don't affect time of normal page generation, because it does nothing then
Yes, agreed. That is what you say in this thread, and that is what we observe, but that is not what is said in the description of the mod
vB Global Translator - Multiply your indexed pages & put search traffic on autopilot Details »»
About Developer
Uses Plugins 
No support by the author.
07-18-2009, 06:18 PM
I use them all 
