I think you'll find that the more commands you implement aside from those trig functions, the less advantage you will have using lookups. They benefit greatly from being able to use the processor cache and it seems to work best when you have one trig command after the other.
It's not particularly real world, but to do a real world test is going to take a lot of time and effort, and the differences will be too insignificant to measure.
It seems clear enough that under BlitzPlus, when doing a lot of trig operations sequentially, there can be some advantage in using lookup tables, but otherwise your optimisation effort is best spent elsewhere I think, and particularly if you're using Blitz3D, where there is a small or even negative difference.
I still wouldn't mind knowing why there is such a big difference in maths performance between the two though. Blitz3D would come out 5 times faster for maths operations than BlitzPlus in my tests.
Anyway, I've said enough.
It's not particularly real world, but to do a real world test is going to take a lot of time and effort, and the differences will be too insignificant to measure.
It seems clear enough that under BlitzPlus, when doing a lot of trig operations sequentially, there can be some advantage in using lookup tables, but otherwise your optimisation effort is best spent elsewhere I think, and particularly if you're using Blitz3D, where there is a small or even negative difference.
I still wouldn't mind knowing why there is such a big difference in maths performance between the two though. Blitz3D would come out 5 times faster for maths operations than BlitzPlus in my tests.
Anyway, I've said enough.