RatOS Mainsail taking upwards of 7 minutes to display frontend
So this used to be pretty fast: turn on printer, wait about a minute, load frontend in Edge or Chrome, profit! Now, it takes upwards of 7 minutes. Tested on multiple machines and multiple browsers. Even on an iPhone and iPad in Chrome and Safari. Results vary slightly but overall it is the same. Takes minutes to load. Attaching a video of an entire load process. The system is recently booted up. First, I wanted to show that I can get to the webcam streaming without issue, and you'll see in the opening seconds that I can see real time streaming without an issue. Then I try to load Mainsail for the first time. Takes close to 7 minutes in this run. Also attaching the logs. Really hope someone can help me figure this out.
19 Replies
what does the timing say it is spending it's time on? This is just an example from me loading discord
How do I get there?
Edit: Nevermind. Found it.
Here it is.
you have to click on the request that is taking a long time (in this case the websocket that is 6th from the top)
that isn't the same screen you showed in the video. and it is hard to tell in this view if that websocket is the one that is taking a long time
It's the shot from the developer tab, from the same vcore3.local address. I'll do a new video. Would that be better?
I know from past interactions with you, that you have installed extras like telegram bot and such. Think about what you have installed and if any of those things are requesting data before loading
@blacksmithforlife You said you wanted the websocket, however I was unsure if you wanted the timing separator or another, so I grabbed all 4.
1427 files?
I wouldn't know. Is that not supposed to happen?
Should I maybe delete something?
I don't know - I can only look at what you are sending
Is there anything I can do to convey better information?
You probably want a developer to debug it locally. With that said, how many files do you have in "G-Code Files" tab?
One. I recently deleted all files thinking it could be a "cache" issue, so to speak.
yeah I have no idea without being there local to debug. Maybe you could try reaching out on the mainsail discord
Worth a shot. Thanks for trying, though.
Did you ever get an answer from the mainsail team about what is causing this?
No. I ended up SSHing into the instance and deleting every single cached file from my telegram bot and also turned of the time-lapse function. Didn't seem to help. Then I reduced my video stream from 1080p @5fps to 720p @3fps. That seemed to decrease the CPU usage some 15%. Still took a long time to log in. Then, after a couple of days, I realized the issue seemed to have resolved itself. I have debated if I should try to put everything back as it was, one at a time, to see if it happens again. However, since it is working well enough as is, I decided against it. The low streaming video is the worst part. But there are worse things in life.