Slow application startup times in some projects

[ernest4]

Hey, awesome work with motion. After spending so much time on React and the 'front end rendering revolution' i think it's about time for a 'back end rendering revolution' :)

Front end code via back end ruby, that's just pure magic :D

Anyway, I'm not sure if this is normal or something wrong with my setup, but it takes at least 5 minutes to start the rails server locally.

Before I installed motion it was about 5 seconds or so.

Wondering this is so long and if normal, will there be speed improvement in this in the future?

Thanks.

[alecdotninja]

Hmm, that has not been my experience. It sounds like a bug.

@ernest4 Does this happen for you locally with the motion-demos project?

[ernest4]

Cool. I'll try to get those running and see.

[ernest4]

So the the motion-demos start up quick for me, in a few seconds as normal. But my own project takes minutes.

[alecdotninja]

@ernest4 Are you able to reproduce the problem in a minimal project that you are willing to share publicly so that I can take a look?

[ernest4]

I'm a long time lurker, first time issue poster on Github, so I'll give it a try :D

I just basically fork my own project repo and strip out as much as I can while the issue still appears to happen right.

Could be a while, since i'll need to strip out bit by bit until I see the issue disappears.

I'll try that later today 👍

[ernest4]

So good news is my start up time is quick again. Bad news is I don't know what the issue was.

All I did was pull down my own repo into another folder in preparation to take things out. Then ran rails server and started up in seconds.

Tried the same with the old project folder - still slow.

Something other must be up with that old project folder, just noticed that sidekiq was also unable to start quickly (or at all, didn't wait forever to find out), while it started fine on the new folder.

So, while still a mystery, I guess it's not a motion specific issue. Sorry about about that :D

[latortuga]

@ernest4 one thing I've noticed can have an effect on startup time is your bootsnap cache. Especially if you've upgraded ruby versions without clearing it out. You can safely delete the bootsnap folder and file inside #{Rails.root}/tmp/cache and retry to see if it was that. A fresh checkout to a new directory would definitely act like you describe - faster for no reason.

[ernest4]

Seems like a good theory, especially as the repo doesn't have the tmp folder and neither does the new project folder.

But I've deleted tmp and it didn't seem improve the situation.

I try to ls -lah and delete any other extra file I've found that the old repo has an new one doesnt, but no luck.

[spencersteiner]

Not sure if mine is a version compatibility issue (running rails 5.2.2 with ruby 2.5.1 for reference) the readme makes reference to rails 6.1, but doesn't explicitly state it as a requirement (if it is, please correct me) -- but I experience the same issue @ernest4 described. I'm still testing, but as soon as I delete the motion initializer config my web server launches in ~5 seconds (compared to several minutes with it included).