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
Default to processor count concurrent scan instead of 2 * processor count #11569
Default to processor count concurrent scan instead of 2 * processor count #11569
Conversation
We will also need to update the placeholder value in the web settings. |
This isn't a 10.9 feature iirc. Isn't defaulting to 1 a step backwards? |
Before 10.9 it was defaulted to just ProcessorCount (3982b0e#diff-41e6711494c9c6ceb7d6aab39d16245177564b0711e402cb2c757d37c3b6815eL589) We can change the default back to that if desired |
Yes I think that's the correct solution here. |
* Fix migration with special Rating (jellyfin#11541) * Add metrics collector to disposable parts (jellyfin#11539) * Fix absolute path checking on windows (jellyfin#11570) * Default to processor count concurrent scan instead of 2 * processor count (jellyfin#11569) * Change "try" to "attempt" english translation (jellyfin#11578) * Bump version to 10.9.1 --------- Co-authored-by: Cody Robibero <cody@robibe.ro> Co-authored-by: gnattu <gnattu@users.noreply.github.com> Co-authored-by: Tim Gels <43609220+TimGels@users.noreply.github.com> Co-authored-by: Jellyfin Release Bot <team@jellyfin.org>
Default to processor count concurrent scan instead of 2 * processor count Original-merge: f77a5d0 Merged-by: crobibero <cody@robibe.ro> Backported-by: Joshua M. Boniface <joshua@boniface.me>
No description provided.