Update bitmagnet-io/bitmagnet Docker tag to v0.9.3 #706
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v0.8.0->v0.9.3Release Notes
bitmagnet-io/bitmagnet (bitmagnet-io/bitmagnet)
v0.9.3Compare Source
This release reduces the default
processor.concurrencyconfig to1following user feedback that concurrency of3causes slowdowns on some systems. If your system can handle it, you may want to configure a higher value.What's Changed
Full Changelog: bitmagnet-io/bitmagnet@v0.9.2...v0.9.3
v0.9.2Compare Source
Some users have reported a slowdown in the app that is probably due to the 0.9.0 reindex. Adding a configuration option to dial down the queue concurrency for torrent processing.
If you're affected, try setting the value to 1, either as an environment variable, e.g.
PROCESSOR_CONCURRENCY=1, or in your config file:What's Changed
Full Changelog: bitmagnet-io/bitmagnet@v0.9.1...v0.9.2
v0.9.1Compare Source
This release includes an optimization may improve reprocess performance on more modest hardware.
What's Changed
Full Changelog: bitmagnet-io/bitmagnet@v0.9.0...v0.9.1
v0.9Compare Source
v0.9.0Compare Source
--apisDisabledflag was added to the reprocess command to allow significantly faster reprocessing/classifying without any API calls (i.e. TMDB), without disabling this globally.bitmagnet reprocess, this is handled by the newprocess_torrent_batchtask)IMPORTANT: Some refactoring of the database was needed to allow for performant ordering. On first run, a database migration will be applied that should take no longer than a few minutes, and tasks will be added to the queue to reindex all torrents. The reindex tasks must complete before ordering will work correctly; if you have millions of torrents in your index this may take a day or more, but is significantly faster in this release than prior versions. Please ensure you have no pending items in your queue (at the
/metricsendpoint) before opening any issues about incorrect ordering.What's Changed
New Contributors
Full Changelog: bitmagnet-io/bitmagnet@v0.8.0...v0.9.0
Configuration
📅 Schedule: Branch creation - "after 3am on Sunday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.