Quote Originally Posted by 'Tdog',index.php?page=Thread&postID=204757#post204 757
So my best guess is that something is getting backed up when I change the master causing Jamba to run really slowly. I doubt it's any of the other addons I have installed as I have disabled everything on all toons except Jamba and it still does the same exact thing for the same amount of time. When I do not switch masters however I never experience this problem, or least not in the last week and a half I've had this installed.

Any help is appreciated
Yup; it's Jamba swamping the addon channel with too much information. You can reduce what your toons send to each other. I suggest turning off the Forward UI Errors and Forward UI Information options in the Jamba-Talk options. This should help a lot.

If you have macros that use jamba commands that use tags; you can minimise traffic by duplicating the macro on all the toons and removing the all tag. (Sorry I can't explain this further right now.)

Jamba uses the Ace3 library which in turn uses ChatThrottleLib. ChatThrottleLib is designed to make sure your characters don't get disconnected when sending addon traffic. Hence when Jamba sends too much information over the wire, you see delays and this is ChatThrottleLib managing the addon traffic. ChatThrottleLib will halve its output rate if your toons FPS is below 20. This sucks for most of us as our slave FPS is usually between 5 - 15.

A solution to this is to make sure all your toons have a minimum of 21 FPS. Another solution is to find all instances of ChatThrottleLib.lua in your Interface/Addons folder and change this line (its near the top of the file):

ChatThrottleLib.MIN_FPS = 20 -- Reduce output CPS to half (and don't burst) if FPS drops below this value

Glad you like Jamba and I hope some of what I have said helps!