Sperson xxxscottyxxx what seems basic usually has a lot of technical detail that goes into it. You canāt just have an infinitely large list of items being returned to the user. At some point you will reach threshold limits either in storage, logic, or display.
You're right in principle, but I think that's unlikely in this case. So that an infinite list is not loaded, there is a pagination. With the help of the pagination, only a certain number of data records is queried from the database. This is not a very computationally intensive process.
From the technical principle, it shouldn't behave very differently from any other filtering of the data. If we take a tag like "brunette" as an example, we have almost 6000 videos in there. Here it also works without threshold limits.
Of course, I don't mean to say that this is all easy to develop. However, it must be said that a few thousand datasets should not pose a problem unless they have not been developed particularly efficiently in one place or another.
Without knowing the structure of the system in detail, I assume a classic system, which roughly consists of the following components:
- Database
- API server
- Clients (Vue website, apps)
In my estimation, one of the two, or even both problems could apply:
- Table with the data of the playlists (e.g. watch later) does not have an optimal structure and is therefore inefficient and slow.
- A Bug in the API Server Endpoint for querying playlist data.
But since none of us knows exactly how the whole thing is technically structured, it's only a guess in the end.
@ devteam: We wish you the best of luck in solving the problem.
