-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
zeopack taking very long to finalize after replacing old storage #274
Labels
Comments
Likely related to generating the index file (created 32 minutes after replacing the Data.fs).
The site contains one fresh Plone installation (result of a full export-import migration) with about 100.000 content objects and 25.000 blobs..The blob storage is mounted on NFS..perhaps that might be the issue? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
ZODB 5.5.1, Python 3.7.3
I packed a filestorage with 30 GB size down to 11 GB. After replacing the Data.fs with the packed version it took about 30 further minutes until zeopack actually finished. What's happening after replacing the Data.fs? Is this due to writing a new index or just Python garbage collection taking place?
Local resource issues are unlikely the problem (decent CPU, enough RM, SSD, no swapping)
The text was updated successfully, but these errors were encountered: