Firmware: Seems to run slow about micropython_k210_lobo HOT 4 CLOSED

It has nothing to do with the calculation speed, but with loop execution speed.
There is a VM hook enabled (MICROPY_VM_HOOK_LOOP) which handles keyboard interrupt during bytecode execution, but in a very inefficient way.
Without it enabled the times are:

System freq: 398.7 MHz
Add test:  2.834 s
Mul test:  3.183 s
Div test:  3.072 s
Pi test:  4.435 s

System freq: 806.0 MHz
Add test:  1.401 s
Mul test:  1.573 s
Div test:  1.471 s
Pi test:  2.173 s

I'll try to implement this hook in a different, more efficient, way.
Also some other optimization can be done to improve the performance...

from micropython_k210_lobo.

OK. Minor differences do not matter. The fastest device with that test is anyhow the PyBoard, mostly due to the traditional internal RAM. But at 800MHz, the K210 comes close, but at much higher power consumption.

from micropython_k210_lobo.

I've tested a different approach for keyboard interrupt and it now works without impacting the performance.
I'll test it some more, and commit it tommorow.

BTW, the floating point operations are faster than on PyBoard, especially considering the fp operations are double precission...

from micropython_k210_lobo.

I've noticed that. The Pi test which makes heavy use of floats runs much faster. And there are more goodies in having 64 bit ints and double floats.
About the change: do not hurry. I just got another task to accomplish form my daughter. That's topmost priority.

from micropython_k210_lobo.