pull down to refresh

I have been having issues with my start9 heating up sporadically to like 85-90 celsius. Yesterday I switched from knots back to btc core and it seems to have resolved the issue (needs more time to be sure).
Anyone else experienced this between knots and core ?
It seems like such a weird installation on Start9, because it looks as if both are running. I never had an overheating issue, but my server was completely funky for a while. I got help from Start9 support. They thought it was my datum installation, not Knots. Then they weren't sure. I did a re install and everything has been okay. Are you running datum?
reply
oooo, yes i was. I switched to core so now my datum is off as it does not work with core on Start9. Interesting so could have been that the whole time.
reply
134 sats \ 8 replies \ @siggy47 9 Sep
All I know is my trouble started when I started running datum.
reply
i believe you. I'll try switching back someday soon...used up my 'server FAFO' time for the week hahah
reply
I know the feeling.
reply
i wonder what it is specifically DATUM is doing to make the server go cray...encryption ?
reply
You're asking the wrong guy! I don't know. Maybe some more knowledgeable Start9 users will weigh in.
reply
id ask in their matrix group but i already been talking with them too much about something else today hahah
201 sats \ 1 reply \ @dgy 9 Sep
Yes, the default configuration of Knots is using more resources. The virtual memory grabbed is about factor 4x more than Core.
If you have enough available memory, you may consider to increase dbcache property in bitcoin.conf. That may help
reply
interesting. So i think the combo of DATUM + knots was wreaking havoc on my server.
reply
Yes, knots is very resource hungry in comparison to core.
reply
My Umbrel has been acting up too since I installed Knots + Datum. I guess the recent attacks on Knots data limits could be a reason too.
reply
mmm maybe, good addition
reply
Been perfect for me. Running Knots on my Start9 for a while now.
reply
I think DATUM was the culprit.
reply