-
Notifications
You must be signed in to change notification settings - Fork 768
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OTP 27.2 exploration #4429
base: master
Are you sure you want to change the base?
OTP 27.2 exploration #4429
Conversation
✅ Deploy Preview for teslamate ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
To test users can follow: https://docs.teslamate.org/docs/development#testing-with-our-ci-which-builds-the-docker-images-automatically-per-pr with |
b59c501
to
98370c8
Compare
98370c8
to
e1cde35
Compare
@leewillis77 @baresel @plutonn @s56oa - could one of you test this PR to see if topic of high cpu usage is still existing in newer versions |
e1cde35
to
f593b37
Compare
Happy to test this tonight, although I can't remember precisely how to do that - can you confirm what I'd need to set the docker image to? |
Oh, actually - is it just |
hi @leewillis77 - yes, for the teslamate image it would be
|
Hello,
tried it and immediately after starting teslamate the beam.smp is consuming
between 85 and 160 percent CPU.
Reverted back to latest version it consumes less than 1 percent.
Am Mo., 20. Jan. 2025 um 13:34 Uhr schrieb Matthias Wirtz <
***@***.***>:
… hi @leewillis77 <https://github.com/leewillis77> - yes, for the teslamate
image it would be
image: ghcr.io/teslamate-org/teslamate:pr-4429
—
Reply to this email directly, view it on GitHub
<#4429 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKURCC72EKV6NMUWIB5VVZT2LTUMBAVCNFSM6AAAAABTG5Z6JGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMBSGMYTCMRTGY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
/ ok, thanks for testing - so staying on otp 26 |
OTP brought performance issues, that's why we are sticking at OTP 26. -> #4319 / #4307
As 27.1.3 has been released, let's try and see if regressions have been resolved.