Light Mode

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Startup performance with large data directory #1149

Answered by felddy
eryon asked this question in Q&A
Startup performance with large data directory #1149
Jan 29, 2025 * 1 comments * 2 replies
Answered by felddy Return to top
Discussion options

eryon
Jan 29, 2025

I have a very large data directory due to using multiple pf2e art compendiums and the jb2a animation pack (total size is ~8 GB). As a result, it takes about 5 minutes for my server to start due to the permission operation. I can't move these packs to a read-only volume because they get updated through Foundry package management.

Is there anything I can do to help this operation complete faster?

Sample startup process, see the timestamps of the last two logs:

foundry | Entrypoint | 2025-01-28 17:40:23 | [debug] Installation completed.
foundry | Entrypoint | 2025-01-28 17:40:23 | [info] Preserving release archive file in cache.
foundry | Entrypoint | 2025-01-28 17:40:23 | [debug] CONTAINER_CACHE_SIZE is not set. Skipping cache cleanup.
foundry | Entrypoint | 2025-01-28 17:40:23 | [debug] Patching GUI update and configuration messages.
foundry | Entrypoint | 2025-01-28 17:40:23 | [info] Not modifying existing installation license key.
foundry | Entrypoint | 2025-01-28 17:40:23 | [info] Setting data directory permissions.
foundry | Entrypoint | 2025-01-28 17:40:23 | [debug] Setting ownership of /data to foundry:foundry.
foundry | Entrypoint | 2025-01-28 17:45:04 | [debug] Completed setting directory permissions.
You must be logged in to vote

Take a look at:

Also, since the v13 release is getting nearer I'll mention that CONTAINER_PRESERVE_OWNER will be deprecated in that release as the container will no longer run as root and have the ability to change ownerships.

See:

View full answer

Replies: 1 comment 2 replies

Comment options

felddy
Jan 29, 2025
Maintainer

Take a look at:

Also, since the v13 release is getting nearer I'll mention that CONTAINER_PRESERVE_OWNER will be deprecated in that release as the container will no longer run as root and have the ability to change ownerships.

See:

You must be logged in to vote
2 replies
Comment options

eryon Jan 29, 2025
Author

I added CONTAINER_PRESERVE_OWNER=/data/Data/modules/jb2a_patreon\|/data/Data/modules/pf2e-tokens-* but it hasn't changed the startup time at all. I appreciate that v13 will change things, so I can live with this until then if there isn't an obvious answer :)

Comment options

eryon Jan 30, 2025
Author

On further inspection, I found that I have a volume mount that needed to be ignored, too.

This did the trick, as indicated by the linked issues

CONTAINER_PRESERVE_OWNER=/data/Data/assets\|/data/Data/modules/jb2a_patreon
Answer selected by felddy
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
2 participants