-
-
Notifications
You must be signed in to change notification settings - Fork 147
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
[BUG] Very high IO wait on initial launch #257
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
I modified /root/etc/s6-overlay/s6-rc.d/init-calibre-web-config/run as follows and it appears to work:
|
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
Any chance my patch (above) is suitable? |
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
@mpatton125 We pushed a fix for lsiown, can you please check if the problem is fixed now? |
@quietsy - I can confirm the fix works as expected for me. No more huge spikes of IO wait. Many thanks. |
Is there an existing issue for this?
Current Behavior
Due to the chown present when the image is initially launched, my system faces very high IO wait that impacts the rest of my system activities.
To put this in context I have a very large library with over 570000 books and more than 1 million files under /app/calibre-web/cps/cache (bind mount to the host for persistence).
Would it be possible to replace the global chown with a find that applies a chown only to files without the correct ownership already?
Expected Behavior
Only files that were not owned by abc.abc should be chown'ed.
Steps To Reproduce
Environment
CPU architecture
x86-64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: