Slow first connection

[avillev]

( sorry I cannot take a look at the code myself, PHP is... not something I master )

I wanted to talk about first display time.

My environement:

• Movary on docker on synology with a SQLlight
• 2545 movies

"Simptoms":

After not using it for a long time, the first load can take a very long time. Sometimes even leading to an nginx timeout (ok after refresh).
Subsequent operations are relatively fast.

My assumptions:

I assume that after a long time, a lot of things need to be loaded/cached from the DB and that explains the very long first load.

My questions:

• Maybe the timeout configuration of Nginx is a little optimistic. Is it configurable? Or should we increase it?
• What is the first load behavior here? Is it conceivable to do things in a more lazy-loading manner? Or maybe prepare/cache in advance the results of the main dashboard beforehand in separate tables for quick requests?

[leepeuker]

hey, thanks for reporting your experience. we have a related GitHub issue about the dashboard performance here, I believe this should have the biggest performance impact.

I will try to look into it in the coming weeks

FYI I have ~1k movies and my dashboard load time with a hard reload in firefox is ~1,1 seconds, not perfect but at least no timeouts yet it seems 😅

[avillev]

That improvement on the other ticket makes sense though. But i doubt it'd turn my 1 minute load into 1 second lol

[leepeuker]

Are you using a proper mysql?

Yes I am, but I think that should not make much of a difference 🤔

The demo has a few more movies than I do and is using sqlite. A hard reload takes about 1 second there as well. The demo is running on a CPX21 (3 shared vCPU and 4GB ram) Hetzner server, so not a potato but nothing fancy either.

[avillev]

I understood the problem. All of my docker images on my server restart at midnight.

So it is quite literally the first time after a restart in movary's Life cycle that will take a very very long time. I assume connecting to the database or something I don't know.

After that initial call, everything is all right.
Maybe I will just do a wget to to alleviate the problem. Or maybe it's something we could consider inside the image itself after boot ?

[avillev]

Ha yeah no, a wget would only get the static page...

[leepeuker]

So it is quite literally the first time after a restart in movary's Life cycle that will take a very very long time.

I will try to look into this when I find the time. Maybe some more debug logging to find the exact cause of the issue could help 🤔