For real time embedded you need to use C, C++ or Rust perhaps. Python is not real time and can be very slow in comparison.I am trying to understand why my code is so slow. because I am developing a real time embedded processing application. A/V capture and processing all in real time. No need for display.
My processing is certainly less complex than video codec. I know the complexity of these codecs as I worked on the HW part of video and telecommunications processing in the.....90's.
First step, evaluating time of data transfer. isn't it obvious ? And even this part, with no other processing is not real time.....
Today, HW speed is around nanoseconds (1Ghz processing time) and memory access (RAM and SD card) is between 10 and 30ns. These are from specs.
Few SW code lines, and all this drops to 330 ns.
So, conclusions are that :
1/ there is still work to do on my side, I am aware of
2/ SW needs to go green, because overheads and layers consumes too much resources
When we are working on video applications here, we get down to assembler and saving one or two instructions in loops as that can mean hitting a frame rate or not. You should also be looking at NEON acceleration as well. The compiler can use NEON, but I think for real performance you need to get your assembler hands dirty.
Statistics: Posted by jamesh — Sun Jul 28, 2024 3:11 pm