You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using ESP32 for wifi and bluetooth packet sniffing, using monitor mode of ESP32 wifi stack and using ESP32 BT/BLE stack.
I assessed that with latest build of esp-idf libraries the overall performance on both wifi and bt sniffing decreased dramatically.
Test setup were 2 identical hardware boards with identical application software. One application software was compiled with esp-idf libraries build before 26th Nov. 18, and the other one after this date.
The board build with latest code sniffs ~60% less bluetooth and ~30% less wifi devices compared with that one build on older code (under same conditions in same time).
I have no idea how to further analyze this. Since both BT and Wifi are affected this could mean a general performance drop on core 0 (running BT and Wifi stack), or a problem with the 2,4 GHz radio driver?
My code for bt and wifi sniffing can be found here:
I am using ESP32 for wifi and bluetooth packet sniffing, using monitor mode of ESP32 wifi stack and using ESP32 BT/BLE stack.
I assessed that with latest build of esp-idf libraries the overall performance on both wifi and bt sniffing decreased dramatically.
Test setup were 2 identical hardware boards with identical application software. One application software was compiled with esp-idf libraries build before 26th Nov. 18, and the other one after this date.
The board build with latest code sniffs ~60% less bluetooth and ~30% less wifi devices compared with that one build on older code (under same conditions in same time).
I have no idea how to further analyze this. Since both BT and Wifi are affected this could mean a general performance drop on core 0 (running BT and Wifi stack), or a problem with the 2,4 GHz radio driver?
My code for bt and wifi sniffing can be found here:
Wifi sniffing
BT sniffing
The text was updated successfully, but these errors were encountered: