Turbo?

msboy1

Well-Known Member
Howdy Y'all,

I just saw the changes in svn to turbo in eq2bot. What does turbo actually do in reference to ISXEQ2 or Innerspace? I couldn't find anything in the wiki about it.

Thanks for your time.
 

Cr4zyb4rd

Active Member
It's part of the Innerspace kernel command set:
http://www.lavishsoft.com/wiki/index.php/Command:Turbo

In short, this command tells innerspace how many lines of script to parse/execute each frame. However, there's a lot of complicated threading that goes on behind the scenes, as extensions and various parts of Innersapce itself take out "frame locks" to make sure various parts of memory don't change while your script code is executing. Also, profiling shows that IS does a pretty good job of "atomizing" blocks of script code during its pre-parsing.

I'm sure some will argue, but I see this command as being more-or-less a holdover from MQ2. There are some situations where it's the right solution to a certain type of bottleneck in script execution, but those situations are few and far between given the way IS works, and chances are that if fiddling with this command gives a script better performance, it's just placing a band-aid on some other problem and could have been fixed another way. Ideally you'll never see it used at all.
 

Pygar

EQ2Bot Specialist
I changed it in eq2bot to see what impact it might have.

Honestly the original setting of Turbo 1000 was completely insane. As I understand how the directive is handled, thats a fairly absurd value. I honestly think the 50 value it is at now is still a very high value.

I don't think the directive controls atom processing, object calls, etc. But may affect the amount of pure script that runs per frame. But as Crazy said, the way it all works isn't as black and white as one would think.

In truth, a script executing too much code per frame is only going to exacerbate lag and cause poorer performance. There aren't that many decisions the bot needs to make in a frame, and it takes a frame for each action it needs to perform based upon that decision. Trying to cram an absurd amount of processing behind each action isn't likely to improve performance, if anything I think it will make a system that performs poorly with the bot even worse.

$0.02

That all being said, if you notice increases or decreases in performance as I tweak this setting, please do share your observations.

Turbo? Natuarally it should be as high as possible, faster is bettah, right? ;)
 
Top Bottom