Program overloading the cRIO?

[ablahblah]

Hey all,
Well, I'm the new designated rookie programmer on my team, 2893, and had to learn Labview pretty much from scratch with no other programming experience, so I'd say only 75% the time I have an idea what I'm actually doing, heh. Anyways, I was wondering what were the possibilities of overloading the cRIO with a Teleop VI? We did a last minute program test in essence, a week before the robot shipped, and the double joystick program I made (with fallbacks allowing each to assume control of the robot, due to our controller failure paranoia), and it didn't work. Error report on the Driver Station reported that the loop was executing too slowly, or something, and was starving the loop. The programmer beforehand inspected my program and came up with 3 options means of why the program failed :
1: I left a case structure blank with nothing to do to the motors in the drive portion of Teleop.
2: I put all my multipliers in the case structures, and according to him doing that loads up the VI more. Also, he's saying that putting multipliers as outside of case structures as possible and instead having the structures feed the multipliers info is a better option (I had tons of little individual multipliers in each case structure doing the same operation, but with different constants).
3: I had wayyyy too many case structures, probably due to the fact that I was linking controllers up to control the robot independently when one fails.

What do you guys think? We haven't tested the program yet, and I'm making changes to fix 1 and 2, but 3 we've no clue whether it would be easy to overload the cRIO in that way.