How safe is it to adjust the Opcodes per Timeslice?
Because I have run some tests and it seems like the firmware becomes unstable when its adjusted to another value from its original 255.
I have attached a zip file with the raw data and the results.
NOTE: These tests were done using the PC-Emulator and not on a physical microcontroller.

It would seem that it isn't safe

- Xander

UPDATE:

I did the benchmarks on an actual Cortex Microcontroller and the results are so different that you can't compare them!
The PC-Emulator is highly flawed!
Anyway, here are the results for the Cortex, they are very promising, up to 40ms faster than default.

charsleysa,

Can we see the program you used to do these tests? Data without information on the actual tests is fairly meaningless

- Xander

DOH! Haha, that may be useful
The code will run each benchmark 30 times on the Opcode setting you choose in the source code.
The output is a CSV file output format which you just save into a CSV file using windows notepad.
On the PC-Emulator the benchmarks are quick but on the Cortex they may take longer, I estimated
that it takes roughly an hour to wait for the benchmarks to finish and push the data into a file.
Enjoy!

Your program doesn't test reliability, only incrementing a variable. You need to test things like motor control and readings sensors. I'd be far more curious to find out how those aspects are impacted by tweaking that variable.

- Xander

As I do not have access to a physical cortex I cannot do those tests, especially since I learned that the PC-Emulator is highly flawed. I will try to put together some code for benchmark IO of the Cortex to its peripherals. But until I score a Cortex and the extra equipment I cant benchmark and report back. I will see what I can do about acquiring the equipment but until then I will later post the source code for the new benchmarks.

So I whipped up some code in a few minutes, but I think its a bit too runty to show any real results.
Anyway to keep consistency I quickly ran through the benchmarks on the PC-Emulator.
As usual, the results were mostly inconclusive because of the instability of the emulator.