I'm aware it's not the fastest, but there's only so much spare money I can throw at the problem. Lemmy is unreasonably resource intensive for baseline functionality.
Alright, a quick update - I have decided to throw a bit more money at lemmy. Database VM has been upgraded from a single core 2GB RAM to dual core 4GB RAM.
I’m not sure what it is, but this didn’t fix the issue at all. I’m using Voyager to access mod logs and when I am signed into my .Cafe account, it’s drags slowly to load anything. Sometimes it takes 5 min or so to load the mod logs.
Whereas any account on any other instance load instantly.
I don’t think the issue is with Voyager, because as I understand, it’s a one rule for all based program.
But either way. This is ONLY a .cafe issue with voyager. Maybe you can reach out to them and see what it may be.
I do see a bit of a correlation of slow modlog and scheduled tasks being run at the same time, but even with that it loads in 20-30 seconds. Which - yes - is atrocious, but at least it fits into tcp timeouts. 5 minutes is straight up mental, can't say why that's happening, yet.
The inbound votes are also somewhat funny. Do people outside lemmy.cafe think that it's slow? Did they miss the sub and thought it was about their instance?
In general - lemmy software is very alpha. It's also possible I have done something wrong on the setup side, however unlikely. I don't want to send any users away, but if you do get fed up with lemmy.cafe - would please let me know at some point if the other instance is substantially better? I could reach out to the admins and ask about their setup.
1
Why when trying to look at modlogs it goes into time out? | Spyke
7 replies
I'm aware it's not the fastest, but there's only so much spare money I can throw at the problem. Lemmy is unreasonably resource intensive for baseline functionality.
This is completely understandable. I was just letting you know that this was happening. Lovely instance otherwise.
Alright, a quick update - I have decided to throw a bit more money at lemmy. Database VM has been upgraded from a single core 2GB RAM to dual core 4GB RAM.
I’m not sure what it is, but this didn’t fix the issue at all. I’m using Voyager to access mod logs and when I am signed into my .Cafe account, it’s drags slowly to load anything. Sometimes it takes 5 min or so to load the mod logs.
Whereas any account on any other instance load instantly.
I don’t think the issue is with Voyager, because as I understand, it’s a one rule for all based program.
But either way. This is ONLY a .cafe issue with voyager. Maybe you can reach out to them and see what it may be.
I hope this helps!
I do see a bit of a correlation of slow modlog and scheduled tasks being run at the same time, but even with that it loads in 20-30 seconds. Which - yes - is atrocious, but at least it fits into tcp timeouts. 5 minutes is straight up mental, can't say why that's happening, yet.
No worries at all. I appreciate that you’re even looking into it. No rush for a fix here. Just hoping this helps a bit.
The inbound votes are also somewhat funny. Do people outside lemmy.cafe think that it's slow? Did they miss the sub and thought it was about their instance?
In general - lemmy software is very alpha. It's also possible I have done something wrong on the setup side, however unlikely. I don't want to send any users away, but if you do get fed up with lemmy.cafe - would please let me know at some point if the other instance is substantially better? I could reach out to the admins and ask about their setup.