I don't know if my Colleagues have similar experience, but using SDK3 causes me almost two times more load of CPU than using 2.6.0 or default 2.6.1.
I tried on two different devices, one has only 2 active relays, ADC and DTH22.
The second one has more sensors but also has very extensive rules, which take up 70% of the memory available for defining rules.
In both cases, the load was always twice as high for SDK3.
In addition, when using SDK3, in the second case (probably due to very complex rules), the device reboot itself 2-3 times a day.
In the case of 2.6.0 and 2.6.1, I haven't noticed self reboots for a very long time.
Is something wrong with SDK3?
Using SDK3 couse duble CPU load
Moderators: grovkillen, Stuntteam, TD-er
-
- Normal user
- Posts: 531
- Joined: 07 Jun 2018, 06:47
- Location: Gdynia/Poland
Re: Using SDK3 couse duble CPU load
Yep, SDK3 has a lot of issues.
See: https://github.com/esp8266/Arduino/issues/5784
And this issue of mine, dating back almost a year ago: https://github.com/esp8266/Arduino/issues/5513
See: https://github.com/esp8266/Arduino/issues/5784
And this issue of mine, dating back almost a year ago: https://github.com/esp8266/Arduino/issues/5513
-
- Normal user
- Posts: 531
- Joined: 07 Jun 2018, 06:47
- Location: Gdynia/Poland
Re: Using SDK3 couse duble CPU load
Well. So we have to wait, believing in a better future ...
Re: Using SDK3 couse duble CPU load
Made me think of this commercial.
-
- Normal user
- Posts: 531
- Joined: 07 Jun 2018, 06:47
- Location: Gdynia/Poland
Re: Using SDK3 couse duble CPU load
In Poland we say: "Man is not a camel. He must drink".....
Who is online
Users browsing this forum: No registered users and 106 guests