@eomanis, 1.6GB should not be a problem. SQLite databases can grow to terabytes in size, with tens of gigabytes not uncommon in applications.
Adobe used it in Photoshop Lightroom to handle metadata for images, web browsers (Chrome, Firefox, etc.) use it for caching, history, cookies, bookmarks and more. The Expensify web application used it in their custom setup to handle terabytes of data and millions of transactions on a single SQLite instance.
However proper database organisation and use of transactions is needed to maintain performance. I understand that the Jellyfin developers have been working specifically on database issues in recent updates, so hopefully the db won't be a performance issue.
Adobe used it in Photoshop Lightroom to handle metadata for images, web browsers (Chrome, Firefox, etc.) use it for caching, history, cookies, bookmarks and more. The Expensify web application used it in their custom setup to handle terabytes of data and millions of transactions on a single SQLite instance.
However proper database organisation and use of transactions is needed to maintain performance. I understand that the Jellyfin developers have been working specifically on database issues in recent updates, so hopefully the db won't be a performance issue.

