Cache more responses from the database

[tjenkinson]

Things like stream urls and media item cover art files should be cached for a few seconds (or longer) as they don't change very often. Each page request shouldn't result in queries to the db to get information like this.

[tjenkinson]

Laravel's built in cache service provider only allows minutes for cache expiration which is not flexible enough.

[stephenrob]

Wouldn't minutes be useful for image assets and stream URLs as they are unlikely to change that often and you can expire the cache on the admin side if you change them ?

[tjenkinson]

Maybe. But even just a few seconds would be a lot better than now which ended up being many times a second when there were many requests.

[stephenrob]

Just thinking about how to make it as simple as possible to implement and setting it to minutes would allow you to use the build in cache service provider.

[tjenkinson]

Yeh. Minutes is too long for things like watching now though. Shouldn't be too complicated to write a separate cache driver that uses redis and allows seconds.

[tjenkinson]

Can now handle when hitting around 90% cpu

• 100 requests a second to a player page

• 100 requests a second to a playlist page

• 100 requests a second to a show page

• 100 requests a second to the shows page

• 100 requests a second to the playlists page

• 70 requests a second to the player information endpoint. Expecting around 50 requests a second for 800 concurrent viewers

[stephenrob]

Is that requests able to be made when the server is around 90% CPU or is that the number of requests that cause 90% CPU ?

100 requests a second to a player page

Also is that a figure for just making a request to the player page or as well as making it to the other endpoints as well ?

Reasonable numbers for current use anyway.

[tjenkinson]

All the 100 ones were actually less than 90% but I didn't bother going higher as I don't think it'll ever get that high. People will only generally load a page once then stay on it.

It's 90% cpu as a result of the requests.

The 100 to player page is just getting the html back for the page. The one below is the ajax endpoint that the player periodically makes requests to get it's urls, view count etc.

I don't think we'll go over 800 concurrent viewers but might get a few more cores added to the vm anyway.