Informative, but maybe no great surprises until the Teensy4.1 ... little rocket, it is.
The ESP32 FreeRTOS integration under Arduino is well done. Creating and distributing tasks between CPU0 and CPU1 is extremely easy:
https://www.hackster.io/rayburne/esp32- ... res-8dd948
What was not shown in the YouTube is the power dissipation per MIP. The ESP8266 can easily have the RF section turned-off to conserve power, but I have not personally verified doing the same with the ESP32.
https://www.hackster.io/rayburne/esp826 ... ime-1df8ae
Other issues to consider, because MIPS is simply a poor comparison choice IMO, is SRAM and flash storage and SPIFFs. (There seems to be some github efforts around SPIFFS for STM32 but I have not investigated the maturity.) For ESP8266, SPIFFs works as advertised and is a no-brainer for look-up tables:
https://www.hackster.io/rayburne/oui-ou ... 266-323ae4
BUT
The "right" uC is the one that fits your project requirements; speed is a very poor choice as the primary attribute of hardware selection. Design and hardware selection is not a guess, rather it is an informed decision with engineering principles applied to the choices.
Understand that increasing the clocking increases the power consumed and the heat that must be dissipated. For battery powered projects, wasted clock cycles is notoriously wasted work at the expense of battery life.
Note that 8-bit uCs are not dead and are an excellent choice for some projects.
WiFi chips can often be excellent general purpose uC's if one disable the radio module.
SPIFFs can be a tie breaker between uC selection; especially in look-up table applications.
Espressif analog performance and available analog ports should be carefully reviewed before uC selection.