As introduced in a separate thread , I believe the database could be improved as follows: PRAGMA synchronous from FULL to NORMAL. Note: The DB is already in WAL mode. PRAGMA temp_store from 0 to 2. Cache size (not default_cache_size) enlarged. Page_size enlarged from 1024 (which is the old def…

Excellent information. I (and I am sure others) appreciate the information and insight from the Plex team. Any public or community response, even one users may not like, is welcomed. Thank you! [image] gbooker02: This (all calls are from one binary) isn’t true. The Plex Media Scanner is run …

Thanks @gbooker02 , for the comments and real info dump! I agree with @jasonsansone about page size. Safe and worthwhile. Can you share what was changed in the last two betas regarding migration speedups?

[image] exuberantShadow: ‘s/SQLITE_OPEN_FULLMUTEX/0x00010000|0x00020000/’ That’s beautiful. I counted the characters in my head, switched to a monospaced font, smiled. I agree they are complementary; I believe FULLMUTEX to be a default. Have you also increased page and cache sizes? I also …

:grin: Yep, this is along with page and cache size changes. Both of those together seem to have made a difference in terms of the logs regarding locked DB. I added SHAREDCACHE in hopes of seeing stable or atleast lower memory usage but the graphs over a few days seemed to be similar to another ins…

I personally haven’t tested the connection changes, but I did change cache_size from 2000 to 8192 and page_size from 1024 to 65536. I haven’t run any benchmarks, but there is a very perceivable improvement on the client front end. FYI - I know the canned response to “I want to speed up the databas…

[image] exuberantShadow: Both of the above reasons led me to remove those flags from any further testing. :+1: That was a long shot anyway. :slight_smile:

[image] jasonsansone: I personally haven’t tested the connection changes, but I did change cache_size from 2000 to 8192 and page_size from 1024 to 65536. I haven’t run any benchmarks, but there is a very perceivable improvement on the client front end. I managed to change the page_size sucess…

Cache_size is set at the time of initiating a db connection, in this instance by the Plex binary. You can’t change it directly on your database like the page_size. In order to change the cache_size you have to edit the Plex binary. [image] Volts: Binary hacking is fun: sed -i.orig \ -e 's/cac…

[image] jasonsansone: Cache_size is set at the time of initiating a db connection, in this instance by the Plex binary. You can’t change it directly on your database like the page_size. In order to change the cache_size you have to edit the Plex binary. Ho, I see, can’t really mess with this …

Just wanted to say, that this is the thread that has the highest chance of a brain meltdown ! When it started, I went to the kitchen to make popcorns, and I’ve been eating them ever since, while feeling more and more impressed ! I humbly bow for the knowledge in the community

Suggested SQLite3 DB Optimizations

Plex Media Server

Volts May 31, 2022, 7:26pm 16

That was a long shot anyway.

Increase paameter value on DB for performance

Topic		Replies	Views
Support Doc for Database Cache Size (MB)? General Discussions server-linux	220	12853	December 29, 2023
Database Cache Size Behavior Question Plex Media Server server-freebsd	9	2298	January 12, 2023
Sqlite3: Sleeping for 200ms to retry busy DB Plex Media Server server-linux	58	482	March 3, 2023
Calling all users with MASSIVE libraries Plex Media Server server-linux	23	527	February 11, 2022
[REQUEST] Move from SQLite to MySQL or Postgres Feature Suggestions	92	9559	June 11, 2022

Suggested SQLite3 DB Optimizations

Related topics