-
Notifications
You must be signed in to change notification settings - Fork 505
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
Jackett can't do multiple searches at the same time #210
Comments
qBittorrent plugin for Jackett is using the "aggregate indexer" to make the requests. That endpoint takes a lot of time (if you have many indexers configured) and it can cause problems if you run several queries at the same time. It will be fixed if we complete this feature someday => #121 |
You can just split your Click here to see instruction
class jackett(object): with class jackett<indexer name>(object):
name = 'Jackett' with name = 'Jackett<indexer name>'
jacket_url = self.url + "/api/v2.0/indexers/all/results/torznab/api?%s" % params with jacket_url = self.url + "/api/v2.0/indexers/<indexer name>/results/torznab/api?%s" % params
jackett_se = jackett() with jackett_se = jackett<indexer name>()
In galeksandrp@jackett-separate-indexers I split As of |
`Jackett` from version [`v0.10.589` Jan 2, 2019](Jackett/Jackett@25ddcb1) does not recommend using `all` indexer. Problem seems to be that many clients including `nova2.py` will wait for `HTTP` request to `Jackett` to finish before starting to process `HTTP` response. This effectivly slows `all` indexer to speed of most slow tracker. While it's possible to process received parts of `HTTP` response before `HTTP` request is finished, `Jackett` instead recommends separate requests to trackers. Finally rework `search` function to: 1. Retrieve `list` of configured indexers. 2. Make request to trackers in parallel threads. Multithreading is chosen instead of multiprocessing because we already in separate process thanks to `nova2.py` `multiprocessing` `main`. Doing `multiprocessing` in `multiprocessing` is questionable matter and actually not working for me (`python` `3.11.0`).
`Jackett` from version [`v0.10.589` Jan 2, 2019](Jackett/Jackett@25ddcb1) does not recommend using `all` indexer. Problem seems to be that many clients including `nova2.py` will wait for `HTTP` request to `Jackett` to finish before starting to process `HTTP` response. This effectivly slows `all` indexer to the speed of most slow tracker. While it's possible to process received parts of `HTTP` response before `HTTP` request is finished, `Jackett` instead recommends separate requests to trackers. Finally rework `search` function to: 1. Retrieve `list` of configured indexers. 2. Make request to trackers in parallel threads. Multithreading is chosen instead of multiprocessing because we already in separate process thanks to `nova2.py` `multiprocessing` `main`. Doing `multiprocessing` in `multiprocessing` is questionable matter and actually not working for me (`python` `3.11.0`).
`Jackett` from version [`v0.10.589` Jan 2, 2019](Jackett/Jackett@25ddcb1) does not recommend using `all` indexer. Problem seems to be that many clients including `nova2.py` will wait for `HTTP` request to `Jackett` to finish before starting to process `HTTP` response. This effectivly slows `all` indexer to the speed of most slow tracker. While it's possible to process received parts of `HTTP` response before `HTTP` request is finished, `Jackett` instead recommends separate requests to trackers. Finally rework `search` function to: 1. Retrieve list of configured indexers. 2. Make request to trackers in parallel threads. `Multithreading` is chosen instead of `multiprocessing` because we already in separate process thanks to `nova2.py` `multiprocessing` `main`. Doing `multiprocessing` in `multiprocessing` is questionable matter and actually not working for me (`python` `3.11.0`).
`Jackett` from version [`v0.10.589` Jan 2, 2019](Jackett/Jackett@25ddcb1) does not recommend using `all` indexer. Problem seems to be that many clients including `nova2.py` will wait for `HTTP` request to `Jackett` to finish before starting to process `HTTP` response. This effectivly slows `all` indexer to the speed of most slow tracker. While it's possible to process received parts of `HTTP` response before `HTTP` request is finished, `Jackett` instead recommends separate requests to trackers. Finally rework `search` function to: 1. Retrieve list of configured indexers. 2. Make request to trackers in parallel threads. `Multithreading` is chosen instead of `multiprocessing` because we already in separate process thanks to `nova2.py` `multiprocessing` `main`. Doing `multiprocessing` in `multiprocessing` is questionable matter and actually not working for me (`python` `3.11.0`).
`Jackett` from version [`v0.10.589` Jan 2, 2019](Jackett/Jackett@25ddcb1) does not recommend using `all` indexer. Problem seems to be that many clients including `nova2.py` will wait for `HTTP` request to `Jackett` to finish before starting to process `HTTP` response. This effectivly slows `all` indexer to the speed of most slow tracker. While it's possible to process received parts of `HTTP` response before `HTTP` request is finished, `Jackett` instead recommends separate requests to trackers. Finally rework `search` function to: 1. Retrieve list of configured indexers. 2. Make request to trackers in parallel threads. `Multithreading` is chosen instead of `multiprocessing` because we already in separate process thanks to `nova2.py` `multiprocessing` `main`. Doing `multiprocessing` in `multiprocessing` is questionable matter and actually not working for me (`python` `3.11.0`).
`Jackett` from version [`v0.10.589` Jan 2, 2019](Jackett/Jackett@25ddcb1) does not recommend using `all` indexer. Problem seems to be that many clients including `nova2.py` will wait for `HTTP` request to `Jackett` to finish before starting to process `HTTP` response. This effectivly slows `all` indexer to the speed of most slow tracker. While it's possible to process received parts of `HTTP` response before `HTTP` request is finished, `Jackett` instead recommends separate requests to trackers. Finally rework `search` function to: 1. Retrieve list of configured indexers. 2. Make request to trackers in parallel threads. `Multithreading` is chosen instead of `multiprocessing` because we already in separate process thanks to `nova2.py` `multiprocessing` `main()`. Doing `multiprocessing` in `multiprocessing` is questionable matter and actually not working for me (`python` `3.11.0`).
`Jackett` from version [`v0.10.589` Jan 2, 2019](Jackett/Jackett@25ddcb1) does not recommend using `all` indexer. Problem seems to be that many clients including `nova2.py` will wait for `HTTP` request to `Jackett` to finish before starting to process `HTTP` response. This effectivly slows `all` indexer to the speed of most slow tracker. While it's possible to process received parts of `HTTP` response before `HTTP` request is finished, `Jackett` instead recommends separate requests to trackers. Finally rework `search` function to: 1. Retrieve list of configured indexers. 2. Make request to trackers in parallel threads. `Multithreading` is chosen instead of `multiprocessing` because we already in separate process thanks to `nova2.py` `multiprocessing` `main()`. Doing `multiprocessing` in `multiprocessing` is questionable matter and actually not working for me (`python` `3.11.0`).
`Jackett` from version [`v0.10.589` Jan 2, 2019](Jackett/Jackett@25ddcb1) does not recommend using `all` indexer. Problem seems to be that many clients including `nova2.py` will wait for `HTTP` request to `Jackett` to finish before starting to process `HTTP` response. This effectivly slows `all` indexer to the speed of most slow tracker. While it's possible to process received parts of `HTTP` response before `HTTP` request is finished, `Jackett` instead recommends separate requests to trackers. Finally rework `search` function to: 1. Retrieve list of configured indexers. 2. Make request to trackers in parallel threads. `Multithreading` is chosen instead of `multiprocessing` because we already in separate process thanks to `nova2.py` `multiprocessing` `main()`. Doing `multiprocessing` in `multiprocessing` is questionable matter and actually not working for me (`python 3.11.0` `Windows 11`).
`Jackett` from version [`v0.10.589` Jan 2, 2019](Jackett/Jackett@25ddcb1) does not recommend using `all` indexer. Problem seems to be that many clients including `nova2.py` will wait for `HTTP` request to `Jackett` to finish before starting to process `HTTP` response. This effectivly slows `all` indexer to the speed of most slow tracker. While it's possible to process received parts of `HTTP` response before `HTTP` request is finished, `Jackett` instead recommends separate requests to trackers. Finally rework `search` function to: 1. Retrieve list of configured indexers. 2. Make request to trackers in parallel threads. `Multithreading` is chosen instead of `multiprocessing` because we already in separate process thanks to `nova2.py` `multiprocessing` `main()`. Doing `multiprocessing` in `multiprocessing` is questionable matter and actually not working for me (`python 3.11.0` `Windows 11`).
`Jackett` from version [`v0.10.589` Jan 2, 2019](Jackett/Jackett@25ddcb1) does not recommend using `all` indexer. Problem seems to be that many clients including `nova2.py` will wait for `HTTP` request to `Jackett` to finish before starting to process `HTTP` response. This effectivly slows `all` indexer to the speed of most slow tracker. While it's possible to process received parts of `HTTP` response before `HTTP` request is finished, `Jackett` instead recommends separate requests to trackers. Finally rework `search` function to: 1. Retrieve list of configured indexers. 2. Make request to trackers in parallel threads. `Multithreading` is chosen instead of `multiprocessing` because we already in separate process thanks to `nova2.py` `multiprocessing` `main()`. Doing `multiprocessing` in `multiprocessing` is questionable matter and actually not working for me (`python 3.11.0` `Windows 11`).
`Jackett` from version [`v0.10.589` Jan 2, 2019](Jackett/Jackett@25ddcb1) does not recommend using `all` indexer. Problem seems to be that many clients including `nova2.py` will wait for `HTTP` request to `Jackett` to finish before starting to process `HTTP` response. This effectivly slows `all` indexer to the speed of most slow tracker. While it's possible to process received parts of `HTTP` response before `HTTP` request is finished, `Jackett` instead recommends separate requests to trackers. Finally rework `search` function to: 1. Retrieve list of configured indexers. 2. Make request to trackers in parallel threads. `Multithreading` is chosen instead of `multiprocessing` because we already in separate process thanks to `nova2.py` `multiprocessing` `main()`. Doing `multiprocessing` in `multiprocessing` is questionable matter and actually not working for me (`python 3.11.0` `Windows 11`).
`Jackett` from version [`v0.10.589` Jan 2, 2019](Jackett/Jackett@25ddcb1) does not recommend using `all` indexer. Problem seems to be that many clients including `nova2.py` will wait for `HTTP` request to `Jackett` to finish before starting to process `HTTP` response. This effectivly slows `all` indexer to the speed of most slow tracker. While it's possible to process received parts of `HTTP` response before `HTTP` request is finished, `Jackett` instead recommends separate requests to trackers. Finally rework `search` function to: 1. Retrieve list of configured indexers. 2. Make request to trackers in parallel threads. `Multithreading` is chosen instead of `multiprocessing` because we already in separate process thanks to `nova2.py` `multiprocessing` `main()`. Doing `multiprocessing` in `multiprocessing` is questionable matter and actually not working for me (`python 3.11.0` `Windows 11`).
`Jackett` from version [`v0.10.589` Jan 2, 2019](Jackett/Jackett@25ddcb1) does not recommend using `all` indexer. Problem seems to be that many clients including `nova2.py` will wait for `HTTP` request to `Jackett` to finish before starting to process `HTTP` response. This effectivly slows `all` indexer to the speed of most slow tracker. While it's possible to process received parts of `HTTP` response before `HTTP` request is finished, `Jackett` instead recommends separate requests to trackers. Finally rework `search` function to: 1. Retrieve list of configured indexers. 2. Make request to trackers in parallel threads. `Multithreading` is chosen instead of `multiprocessing` because we already in separate process thanks to `nova2.py` `multiprocessing` `main()`. Doing `multiprocessing` in `multiprocessing` is questionable matter and actually not working for me (`python 3.11.0` `Windows 11`).
`Jackett` from version [`v0.10.589` Jan 2, 2019](Jackett/Jackett@25ddcb1) does not recommend using `all` indexer. Problem seems to be that many clients including `nova2.py` will wait for `HTTP` request to `Jackett` to finish before starting to process `HTTP` response. This effectivly slows `all` indexer to the speed of most slow tracker. While it's possible to process received parts of `HTTP` response before `HTTP` request is finished, `Jackett` instead recommends separate requests to trackers. Finally rework `search` function to: 1. Retrieve list of configured indexers. 2. Make request to trackers in parallel threads. `Multithreading` is chosen instead of `multiprocessing` because we already in separate process thanks to `nova2.py` `multiprocessing` `main()`. Doing `multiprocessing` in `multiprocessing` is questionable matter and actually not working for me (`python 3.11.0` `Windows 11`).
`Jackett` from version [`v0.10.589` Jan 2, 2019](Jackett/Jackett@25ddcb1) recommends separate requests to indexers instead of single request to `all` indexer. Reason to that is because `Jackett` uses `Torznab` specification, which returns results serialized in single `XML`. This means `all` indexer must wait for all indexers to finish before providing ANY results. This limits `all` indexer to the speed of slowest indexer. Finally rework `search` function to: 1. Retrieve list of configured indexers. 2. Make requests to indexers in parallel threads. `Multithreading` is chosen instead of `multiprocessing` because we already in separate process thanks to `nova2.py` `multiprocessing` `main()`. Doing `multiprocessing` in `multiprocessing` is questionable matter and actually not working for me (`python 3.11.0` `Windows 11`).
`Jackett` from version [`v0.10.589` Jan 2, 2019](Jackett/Jackett@25ddcb1) recommends separate requests to indexers instead of single request to `all` indexer. Reason to that is because `Jackett` uses `Torznab` specification, which returns results serialized in single `XML`. This means `all` indexer must wait for all indexers to finish before providing ANY results. This limits `all` indexer to the speed of slowest indexer. Finally rework `search` function to: 1. Retrieve list of configured indexers. 2. Make requests to indexers in parallel threads. `Multithreading` is chosen instead of `multiprocessing` because we already in separate process thanks to `nova2.py` `multiprocessing` `main()`. Doing `multiprocessing` in `multiprocessing` is questionable matter and actually not working for me (`python 3.11.0` `Windows 11`).
* Make search faster with multi-thread implementation * Show error messages per indexer * Number of threads is configurable in jackett.json config file Based on qbittorrent#222 Thank you @galeksandrp and @WojtekKowaluk
* Make search faster with multi-thread implementation * Show error messages per indexer * Number of threads is configurable in jackett.json config file Based on qbittorrent#222 Thank you @galeksandrp and @WojtekKowaluk
the jackett repo redirected me here
Jackett/Jackett#13551
The text was updated successfully, but these errors were encountered: