This script
in
2 posts,
2 voices
funky farmer
User
|
Is making forefox and travian, laggier and laggier as you add more so some work on this needs to be sorted or makes a few basic scripots which you can add up or something Personally i use half of the feyures at a guess but it makes cata waves not as good as if used without :( shame as the fucntions of the script are good |
ms99
Script's Author
|
@funky farmer,
You could have added this post to the "Issues/Bug Reports" thread. But anyway... I will give you now some execution times for the script functions while on the "dorf1.php" page in the format: function name = time 1 (time2)where: time1 = execution time for an account with 16 villages in ms time2 = execution time for an account with 2 villages in ms getGeneralData = 47 ms (25 ms) hideAd = 1 ms (3 ms) - first on a server without banners and in paranthesis for a server with banners hLToJsVoid = 1 ms (1 ms) showBigIconsBar = 27 ms (21 ms) - only 2 additional big icons activated leftMenuLinks = 12 ms (11 ms) getRace = 1 ms (1 ms) addFillTimeRow = 2 ms (2 ms) getCrtLocation = 3 ms (2 ms) prepareDivDocking = 1 ms (2 ms) villageList = 239 ms (32 ms) show2ndVillageList = 170 ms (42 ms) showDeleteAccount = 1 ms (1 ms) showResBarTooltip = 24 ms (20 ms) showUserBookmarks = 12 ms (0 ms) showNoteBlock = 9 ms (0 ms) showHeroStatus = 1 ms (1 ms) And these are the functions that run on every single page that you open from a game server. As you can see, preparing the extended village list (with the additional icons and numbers) takes a very long time. And it follows... the second floating village list. And the time increases with the number of villages because of the data need to be read/saved every time. By choosing to show less icons in the village list, the time will not decrease dramatically, as the calculations and read/save operations still take place. But by not showing the second village list, you can reduce the execution time of the script. Another big improvement would be to not show the upgrade tables. And another one would be to not show the troop information on all pages (the tooltip that shows the attack/defense power, crop consumption and speed). Even if the size of the script is so big, the getGeneralData function (that reads important data for the script and does the translation to your language) does not take so much execution time. And when you send catas waves, you should disable Greasemonkey. Otherwise you may have surprises and not only because of this script (a page on which another script runs may load unexpectedly, another Travian tab may load because some building has been finished or another troop has finished training, etc.). These are only some of my findings and considerations based on my measurements and observations. They may not apply to you or other players/computers/situations. |
