AlmightySnoo 🐢🇮🇱🇺🇦 to Lemmy@lemmy.mlEnglish • 1 year agoidle Lemmy tab using too much CPU resources?lemmy.worldimagemessage-square14fedilinkarrow-up18file-text
arrow-up18imageidle Lemmy tab using too much CPU resources?lemmy.worldAlmightySnoo 🐢🇮🇱🇺🇦 to Lemmy@lemmy.mlEnglish • 1 year agomessage-square14fedilinkfile-text
I left that tab open for a few hours and when I came back my laptop was really hot and the CPU fans kicked in.
minus-square@EscalinkEnglish1•1 year agoAh, disabling auto updates. So it was just server issue then. Websockets are normally just fine. It shouldn’t cause any cpu issues when implemented properly.
minus-square@Die4Ever@programming.devlinkfedilinkEnglish1•1 year ago when implemented properly it’s probably a buggy implementation which is why they’re disabling it for now, and yea it causes server load too
minus-square@EscalinkEnglish1•1 year agoFair. Bit of a shame though. I always enjoy leaving the comment page open and follow the new comments live as they get posted.
minus-square@Die4Ever@programming.devlinkfedilinkEnglish1•edit-21 year agoeh I don’t really like it cause it messes up your scroll position if you were reading something, easy enough to just manually refresh and sort by new I wouldn’t be surprised if they later fix it and bring it back as an option
Ah, disabling auto updates. So it was just server issue then. Websockets are normally just fine. It shouldn’t cause any cpu issues when implemented properly.
it’s probably a buggy implementation which is why they’re disabling it for now, and yea it causes server load too
Fair. Bit of a shame though. I always enjoy leaving the comment page open and follow the new comments live as they get posted.
eh I don’t really like it cause it messes up your scroll position if you were reading something, easy enough to just manually refresh and sort by new
I wouldn’t be surprised if they later fix it and bring it back as an option